[Webkit-unassigned] [Bug 46165] Focused frame information needed in Chrome and ChromeClient

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=46165





--- Comment #12 from Sam Weinig <sam at webkit.org>  2010-09-24 07:25:48 PST ---
(In reply to comment #11)
> (In reply to comment #10)
> > > 
> > > > I am still not clear on why the user needs to know the name of the focused frame?  What can they do with that information?
> > > 
> > > Sorry, my mistake. I meaned focused frame url.
> > 
> > I am still not sure what the use case is.
> 
> Html-page contains 3 frames(main frame + 2 other) and the user wants to know 
> url of any other frame than a mainframe, it's impossible. 
> WebKit1: QWebPage->currentFrame()->url()
> 
> Html-page contains 3 frames(main frame + 2 other) and the user just wants to
> access the current frame, it's impossible. 
> WebKit1: QWebPage->currentFrame();
> 
> In WebKit2, there is only possibility to operate with the mainframe, 
> not focused or any other than mainframe.

I understand how it can be used, but *why* does a user need to know which frame is focused from the UIProcess.  The model we have been trying to work with is to have almost everything be based on the Page, and have frames act almost as handles to the load state.

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