-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Dart2JS's unwrapException appears to be fragile #7545
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Upon further consideration, I think the problem is our interceptor implementation. Pete: could you provide an example or a bad stack trace? Set owner to @peter-ahe-google. |
Possible fix was committed here: |
Correct, also see: Latest Chrome developer builds changed the error's message and also removed some of the properties so it now looks much more like FireFox. This was the source of the failures in build: Note that we only saw these errors yesterday on the Linux Chrome dev builds, but I assume it will be rolling out more widely. |
Do we know why Chrome removed these properties? Aligning with Firefox is suboptimal for compiling other languages to JavaScript. We need to get some kind of error code, precisely like Internet Explorer provides or Chrome used to provide. Relying on localized strings is dreadful :-( |
I don't have any background on Chrome's change though the new behavior appears to be a closer implementation of the js language spec. |
Added TriageForM5 label. |
Removed this from the M5 milestone. |
Fixed in r25262. Added Fixed label. |
unwrapException relies on the message of the exception to determine what type of Dart exception object it should be, but this appears to be fragile and prone to changes in browsers.
For example, Chrome appears to have recently changed the message when functions cannot be found.
The text was updated successfully, but these errors were encountered: