[Webkit-unassigned] [Bug 208500] [first paint] visually-non-empty state should match FCP spec

[bugzilla-daemon at webkit.org]

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

Geoffrey Garen <ggaren at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ggaren at apple.com

--- Comment #1 from Geoffrey Garen <ggaren at apple.com> ---
Note: In cases where the spec and the implementation differ, we need to consider suggesting a change to the spec in order to match the implementation. It's not necessarily good to change the implementation to match the spec, if doing so would make painting worse.

Specifically, I'm skeptical about these item:

- It has a pixel/character threshold, while FCP doesn't

I'm not sure we want to paint in cases where painting would only render a few pixels; to many users, this may seem like a "flash of white", which can be bothersome just like a "flash of unstyled content".

- It's triggered when the page is ready with no pending requests (this is meaningful only for FCP reporting)

I'm pretty sure we want to paint in cases where there's nothing left to load. Though I don't remember the specifics, I remember we faced some cases where the entire contents of the webpage were too insignificant to trigger any painting according to our VNE heuristics, but we still needed to make sure to paint at page load done time, otherwise, we would never paint.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20200413/c03a1e30/attachment.htm>