Clients want to know that to present different UI on pages with frames.
Created attachment 72259 [details] proposed patch
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.
I can easily add a boolean for the last sent value, but it didn't seem important to me. Should I?
(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.
Sam says it's fine, but he also says that I should be sending a page message, not a process one.
Created attachment 72267 [details] updated patch
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.
Attachment 72259 [details] did not build on qt: Build output: http://queues.webkit.org/results/4826065
Attachment 72267 [details] did not build on qt: Build output: http://queues.webkit.org/results/4857057
Attachment 72267 [details] did not build on chromium: Build output: http://queues.webkit.org/results/4866022
Attachment 72267 [details] did not build on chromium: Build output: http://queues.webkit.org/results/4789077
Committed (with build fixes and comments addressed) in <http://trac.webkit.org/changeset/70894>.
(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?
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.
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...