[Webkit-unassigned] [Bug 91766] New: didFirstVisuallyNonEmptyLayout() callback not fired when about:blank page is modified

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Jul 19 11:32:11 PDT 2012


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

           Summary: didFirstVisuallyNonEmptyLayout() callback not fired
                    when about:blank page is modified
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Layout and Rendering
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: creis at chromium.org
                CC: sam at webkit.org, zbujtas at gmail.com, fishd at chromium.org,
                    abarth at webkit.org, creis at chromium.org


Created an attachment (id=153314)
 --> (https://bugs.webkit.org/attachment.cgi?id=153314&action=review)
Repro page that writes into newly created tabs.

Based on the name, I would expect about:blank pages to not fire the didFirstVisuallyNonEmptyLayout() callback when loaded, since they are visually empty.  Instead, the callback should be fired at the time another window injects content into the about:blank page.

Currently, the callback is fired immediately when using window.open("").  It should instead fire if another window tries something like w.document.innerHTML += "foo" or w.document.write("foo").

Also surprisingly, the callback is not fired at all when using window.open(slow_url).  It appears that this is because FrameView::performPostLayoutTasks is being incorrectly called on the opener window, rather than the newly opened window.  As a result, m_firstVisuallyNonEmptyLayoutCallbackPending is false and the callback is not fired.

Simple repro page attached.  Just attach a debugger and listen to FrameLoader::didFirstVisuallyNonEmptyLayout.

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



More information about the webkit-unassigned mailing list