RESOLVED FIXED48576
Let WebKit2 client know when a frame is a frameset
https://bugs.webkit.org/show_bug.cgi?id=48576
Summary Let WebKit2 client know when a frame is a frameset
Alexey Proskuryakov
Reported 2010-10-28 16:25:11 PDT
Clients want to know that to present different UI on pages with frames.
Attachments
proposed patch (24.30 KB, patch)
2010-10-28 16:50 PDT, Alexey Proskuryakov
darin: review+
updated patch (25.29 KB, patch)
2010-10-28 17:25 PDT, Alexey Proskuryakov
darin: review+
Alexey Proskuryakov
Comment 1 2010-10-28 16:50:37 PDT
Created attachment 72259 [details] proposed patch
Darin Adler
Comment 2 2010-10-28 16:54:45 PDT
Comment on attachment 72259 [details] proposed patch It looks to me like this will send the message more times than it needs to. I can browse pages without any framesets all day long and it seems the message will be sent often during that time.
Alexey Proskuryakov
Comment 3 2010-10-28 16:57:47 PDT
I can easily add a boolean for the last sent value, but it didn't seem important to me. Should I?
Darin Adler
Comment 4 2010-10-28 16:59:45 PDT
(In reply to comment #3) > I can easily add a boolean for the last sent value, but it didn't seem important to me. Should I? I’d ask the WebKit2 architects that question. I’m not sure how important it is to avoid sending unneeded messages between processes, but my assumption is that doing so is worthwhile.
Alexey Proskuryakov
Comment 5 2010-10-28 17:08:19 PDT
Sam says it's fine, but he also says that I should be sending a page message, not a process one.
Alexey Proskuryakov
Comment 6 2010-10-28 17:25:43 PDT
Created attachment 72267 [details] updated patch
Darin Adler
Comment 7 2010-10-28 17:29:55 PDT
Comment on attachment 72267 [details] updated patch View in context: https://bugs.webkit.org/attachment.cgi?id=72267&action=review > WebCore/loader/FrameLoaderClient.h:227 > + virtual void dispatchDidBecomeFrameset(bool) = 0; // Can change back due to navigation or DOM modification. Not sure the word “back” here is helpful. > WebKit2/ChangeLog:31 > +2010-10-28 Alexey Proskuryakov <ap@apple.com> > + > + Reviewed by NOBODY (OOPS!). Double change log.
Early Warning System Bot
Comment 8 2010-10-28 17:41:53 PDT
Early Warning System Bot
Comment 9 2010-10-28 18:11:49 PDT
Eric Seidel (no email)
Comment 10 2010-10-28 20:00:36 PDT
WebKit Review Bot
Comment 11 2010-10-29 06:50:38 PDT
Alexey Proskuryakov
Comment 12 2010-10-29 10:28:32 PDT
Committed (with build fixes and comments addressed) in <http://trac.webkit.org/changeset/70894>.
Nikolas Zimmermann
Comment 13 2010-10-29 13:23:16 PDT
(In reply to comment #12) > Committed (with build fixes and comments addressed) in <http://trac.webkit.org/changeset/70894>. This patch broke lots of tests on the bots. Alexey are you already investigating?
Nikolas Zimmermann
Comment 14 2010-10-29 13:26:47 PDT
Comment on attachment 72267 [details] updated patch View in context: https://bugs.webkit.org/attachment.cgi?id=72267&action=review > WebCore/html/HTMLFrameSetElement.cpp:211 > + if (Frame* frame = document()->frame()) Hm, a call to HTMLElement::insertedIntoDocument is missing here. > WebCore/html/HTMLFrameSetElement.cpp:217 > + if (Frame* frame = document()->frame()) And here a call to HTMLElement::removedFromDocument is missing.
Nikolas Zimmermann
Comment 15 2010-10-29 13:28:29 PDT
Sorry, for the noise. Just read about commit r70907, which fixed the world again. Sorry, just spotted breakage on build.webkit.org/waterfall and had a look at this patch...
Note You need to log in before you can comment on or make changes to this bug.