Status: New
Owner: ----
New issue 2524 by [email protected]: Throwing an exception in
FailedAccessCheckCallback causes weird behavior.
http://code.google.com/p/v8/issues/detail?id=2524
In order to address https://bugs.webkit.org/show_bug.cgi?id=43504, I'd like
to throw a DOM exception from the access check callback that's set via
V8::SetFailedAccessCheckCallbackFunction. Doing so, however, gives me
strange results. Rather than throwing an exception, the whole JavaScript
context seems to be wrong: specifically, things like
`document.getElementById('id')` no longer give me elements that are, in
fact, on the page.
There was some discussion about this a few years ago:
https://groups.google.com/forum/?fromgroups=#!topic/v8-users/5zaAtsqXpG0.
The bug discussed there is fixed (I don't hit an assert), but it seems to
have exposed new behavior that Mihai never checked. :/
Regardless, it's entirely possible that I'm just going about this the wrong
way entirely. If that's the case, I'd appreciate a tip. :)
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
