[Webkit-unassigned] [Bug 25634] Need a way to get the Frame for the code at the top of the JS stack

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri May 8 13:50:51 PDT 2009


------- Comment #4 from aa at chromium.org  2009-05-08 13:50 PDT -------
(In reply to comment #3)
> We almost always want the bottom of the stack.  Why do we want to the top of
> the stack in these cases?

You can check out the related Chromium change. When an Extension API is called,
we want to know which frame invoked it so that we can be more intelligent with
the behavior of APIs based on what RenderView they came from.

For example: we have a createWindow() API. We want the new window be positioned
relative to the window the API call originated from. In order to know which
window the call originated from, we need to know which renderview it originated
from. Since JavaScript calls can traverse frame boundaries, the bottom of the
stack can give the wrong answer.

An easy example of this is the inspector. You can call
chromium.windows.create() from the inspector. We want the new window to be
positioned relative to the window you're inspecting, not the inspector window.

But there are other examples.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the webkit-unassigned mailing list