[Webkit-unassigned] [Bug 91766] didFirstVisuallyNonEmptyLayout() callback not fired for initial about:blank page in new loading window

[bugzilla-daemon at webkit.org]

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


Charles Reis <creis at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|didFirstVisuallyNonEmptyLay |didFirstVisuallyNonEmptyLay
                   |out() callback not fired    |out() callback not fired
                   |when about:blank page is    |for initial about:blank
                   |modified                    |page in new loading window




--- Comment #5 from Charles Reis <creis at chromium.org>  2012-07-19 13:16:43 PST ---
(In reply to comment #3)
> This is a very strange and poorly-named API. We have been considering re-naming it actually.
> 
> (In reply to comment #1)
> > We need to understand the intent of this callback.  It's possible it's just part of the loading lifecycle and should always fire sometime after Commit and before DOMContentLoaded or Loaded.
> > 
> > > w.document.innerHTML += "foo"
> > 
> 
> See these lines in FrameView::performPostLayoutTasks():
> 
> // Ensure that we always send this eventually.
> if (!m_frame->document()->parsing() && m_frame->loader()->stateMachine()->committedFirstRealDocumentLoad())
>             m_isVisuallyNonEmpty = true;
> 
> So yes, the assumption right now is that it should always fire when the above criteria are met.

Thanks, that clarifies things.  I've renamed this bug to be about the loading case.

For my use case (detecting when about:blank is no longer blank), I could perhaps listen to ChromeClient::layoutUpdated and then check whether the page is still empty.  Is there a sane way to check that?  Or a better event to listen to?

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