Updates:
Status: Assigned
Labels: -Pri-2 Pri-3
Comment #2 on issue 21905 by [email protected]: cross-context
callbacks can get lost
http://code.google.com/p/chromium/issues/detail?id=21905
I talked with Aaron and Erik, and we decided this was enough of an edge
case to punt
till later. I did some investigating, though, and the gist of the bug is
that we're
storing callback state in javascript, and that state gets associated with a
context
that is about to be destroyed (because we're navigating away). The same
problem
should theoretically exist with events.
We can fix this by moving that state into C++ in a frame-independent
structure. We'd
also have to fix up our usage of v8::Context::GetCurrent() - this will
return
"other's" context, which again will be destroyed by the time the callback
fires. I
think what we want is GetEntered(), which would return the toplevel context
that is
actually making the toolstrip.expand() call.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
