You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there, first off thanks for an incredible useful collection of modules! 馃憤
Expected Behavior
I would expect StackFrame.functionName to be consistent across browsers.
Current Behavior
The parsed stack from two different browsers (e.g. Safari 11 vs. Edge 14) which originated in the top level of a <script> tag, yields two distinct strings for StackFrame.functionName:
"Global code" (Safari 11) vs "global code" (Edge 14)
Context
I notice that there are test cases for both versions of this string:
Personally I would like the library to normalize this string such that stacktraces are more consistent between browsers but I want to know if it is intentionally like this.
If you agree that it should be normalized, I'd be happy to supply a pull request.
Hi there, first off thanks for an incredible useful collection of modules! 馃憤
Expected Behavior
I would expect
StackFrame.functionNameto be consistent across browsers.Current Behavior
The parsed stack from two different browsers (e.g. Safari 11 vs. Edge 14) which originated in the top level of a
<script>tag, yields two distinct strings forStackFrame.functionName:"Global code"(Safari 11) vs"global code"(Edge 14)Context
I notice that there are test cases for both versions of this string:
error-stack-parser/spec/error-stack-parser-spec.js
Line 47 in 8f4c871
error-stack-parser/spec/error-stack-parser-spec.js
Line 145 in 8f4c871
So I wonder if this is intentional?
Possible Solution
Personally I would like the library to normalize this string such that stacktraces are more consistent between browsers but I want to know if it is intentionally like this.
If you agree that it should be normalized, I'd be happy to supply a pull request.
Cheers!