We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the Resize Observer there is a section about handing resize loops:
https://www.w3.org/TR/resize-observer/#deliver-resize-error
To deliver resize loop error notification run these steps: Create a new ErrorEvent. Initialize event’s message slot to "ResizeObserver loop completed with undelivered notifications.". Report the exception event.
To deliver resize loop error notification run these steps:
However, the step "Report the exception event" is ambiguous. Different browsers handle it differently:
Safari – prints the error message to the console Chrome, Firefox – do not print anything to the console.
Demo: https://output.jsbin.com/vusorevisi
To be fair, all browsers report the error via window.onerror handler, but if it is missing, there is no way to see the error message.
window.onerror
What is the expected result here? Should browsers always print the message, like it happens with unhandled JavaScript errors, for example?
The text was updated successfully, but these errors were encountered:
Related: #5488
Sorry, something went wrong.
No branches or pull requests
In the Resize Observer there is a section about handing resize loops:
https://www.w3.org/TR/resize-observer/#deliver-resize-error
However, the step "Report the exception event" is ambiguous. Different browsers handle it differently:
Safari – prints the error message to the console
Chrome, Firefox – do not print anything to the console.
Demo: https://output.jsbin.com/vusorevisi
To be fair, all browsers report the error via
window.onerror
handler, but if it is missing, there is no way to see the error message.What is the expected result here? Should browsers always print the message, like it happens with unhandled JavaScript errors, for example?
The text was updated successfully, but these errors were encountered: