-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Add new event 'page:error' #2884
Labels
stage: ready for work
The issue is reproducible and in scope
type: breaking change
Requires a new major release version
Milestone
Comments
31 tasks
Will this be a breaking change? I know a lot of users have the |
Yes, it will. |
@chrisbreiding Will this address this issue of listening to |
Closing due to inactivity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
stage: ready for work
The issue is reproducible and in scope
type: breaking change
Requires a new major release version
This will replace the current 'uncaught:exception' event, which is equivalent to when
window.onerror
fires. It will also fire whenwindow.onunhandledrejection
fires.It's called signature should be:
We'll add a
source
property to indicate where it came from ('onerror' or 'unhandledrejection').The user can
return false
to not handle the error.We'll standardize the error from
window.unhandledrejection
, so that there's noreason
property.The text was updated successfully, but these errors were encountered: