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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Apr 13 20:47:44 PDT 2020


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

--- Comment #5 from Geoffrey Garen <ggaren at apple.com> ---
> 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.

> > - 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.
> 
> Yes. In this case, FCP might never trigger. I think this is OK, and was
> discussed on the spec group. FCP may be used to discover bugs, but of course
> WebKit should display the page in this case.

Sounds good!

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


More information about the webkit-unassigned mailing list