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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Dec 4 15:38:37 PST 2012


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


Charles Reis <creis at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX




--- Comment #15 from Charles Reis <creis at chromium.org>  2012-12-04 15:41:03 PST ---
(In reply to comment #14)
> Charles, are you pushing this forward?  It's not clear who's supposed to make progress on this bug, and since it blocks http://crbug.com/9682 it would be good to fix somehow.

It turns out Adam's right-- this is not the right signal for fixing http://crbug.com/9682.  Looking for visual changes is not sufficient for knowing when we have to stop showing the pending navigation's URL.

For example, code injected into the about:blank page could leave the page white but request a permission that shows a prompt/infobar.  We can't have the pending URL visible alongside the infobar.

It seems like we'll need some other signal to tell us that the initial document has somehow "become active" or assumed the security context of another window.  I don't know how that should look yet.

At any rate, this API apparently wasn't designed for the case I was looking for, so I'll mark this as WontFix.  We can further discuss the http://crbug.com/9682 problem on that bug.

-- 
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