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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Mar 2 23:32:56 PST 2020


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

            Bug ID: 208500
           Summary: [first paint] visually-non-empty state should match
                    FCP spec
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Layout and Rendering
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: noam at webkit.org
                CC: bfulgham at webkit.org, simon.fraser at apple.com,
                    zalan at apple.com

Currently visually non-empty state differs from FCP spec in the following ways:
- It can be triggered by an empty canvas
- It does not get triggered by background images
- It has a pixel/character threshold, while FCP doesn't
- It's triggered when the page is ready with no pending requests (this is meaningful only for FCP reporting)

According to an email thread on webkit-dev, we should make an effort to match the spec and the implementation.

-- 
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/20200303/f13e4a15/attachment.htm>


More information about the webkit-unassigned mailing list