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
Look into assert_throws(null, ...) usage #5317
Comments
There's not a lot:
|
@jakearchibald @wanderview for service-workers/service-worker/client-navigate.https.html do you know what the assert_throws(null, ...) can be replaced with? Is this just cross-origin access that should fail? So should be as easy as s/null/"SecurityError"/? |
I'm in the middle of fixing some other problems in this test here: https://bugzilla.mozilla.org/show_bug.cgi?id=1351935 I just tried updating my patch to also use "SecurityError" here and it passes in FF. And yes, these checks are just to verify the iframe is actually treated as cross-origin. Do you want me to just fix this while I'm in the middle of changing the other parts of the test? That way we could avoid conflicting. |
@wanderview that would be great, thanks! |
I realize we added this to make sure stuff would at least throw, but that shows up even if you request a detailed exception. Furthermore, somehow we ended up masking a failure in Chrome for [[PreventExtensions]]. (I’m not sure how, but there’s a difference in the results.) Removing this helps fixing #5317.
I realize we added this to make sure stuff would at least throw, but that shows up even if you request a detailed exception. Furthermore, somehow we ended up masking a failure in Chrome for [[PreventExtensions]]. (I’m not sure how, but there’s a difference in the results.) Removing this helps fixing #5317.
All exceptions should be well-defined, so any such usage is arguably a bug. Perhaps with some work it can be removed.
The text was updated successfully, but these errors were encountered: