[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

--- Comment #6 from Noam Rosenthal <noam at webkit.org> ---
(In reply to Geoffrey Garen from comment #5)
> > The current pixel/character heuristic raise a lot of questions...
> 
> Indeed!
> 
> > But for now, as I understood what was agreed (see above comment link) is
> > that FCP doesn't count pixels/characters but VNE would still block painting
> 
> Hmmm... does that comment suggest that it's OK to report FCP even if we have
> not painted? Seems like that might mislead web developers, if they trigger
> the case where there's a difference.
No, in any case in WebKit FCP would also be blocked by VNE. It means that in some cases in WebKit FCP would happen a bit later than what's in the spec because of this blocking. This meta-bug has tried to reduce these cases to a minimum, and now since the dependencies are closed, the only cases where VNE would block FCP reporting are where the pixel-count/character-count is below the threshold.

-- 
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/20200414/eff0615c/attachment-0001.htm>