Bug 222245

Summary: [Paint Timing] Return early from contentful paint check when no contentful pixels/characters at all
Product: WebKit Reporter: Noam Rosenthal <noam>
Component: Layout and RenderingAssignee: Noam Rosenthal <noam>
Status: RESOLVED FIXED    
Severity: Normal CC: bfulgham, cdumez, esprehn+autocc, ews-watchlist, kangil.han, sabouhallawa, simon.fraser, webkit-bug-importer, zalan
Priority: P2 Keywords: InRadar
Version: Other   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=222186
Bug Depends on:    
Bug Blocks: 211736    
Attachments:
Description Flags
Patch none

Noam Rosenthal
Reported 2021-02-21 03:48:18 PST
The MotionMark tests captured an edge case that causes expensive contentfulness computations. See https://browserbench.org/MotionMark1.1/developer.html (Focus/Multiply tests) This edge case is not plausible in real websites, but happens in this benchmark: - There are lots of elements, performing rendering-intensive rendering - There is nothing "contentful" in the page, so "first contenful paint" has to be computed multiple times.
Attachments
Patch (2.69 KB, patch)
2021-02-21 03:53 PST, Noam Rosenthal
no flags
Noam Rosenthal
Comment 1 2021-02-21 03:53:05 PST
Simon Fraser (smfr)
Comment 2 2021-02-21 09:23:53 PST
Comment on attachment 421136 [details] Patch If the test elements contained one glyph each, what would happen?
Noam Rosenthal
Comment 3 2021-02-21 10:09:42 PST
(In reply to Simon Fraser (smfr) from comment #2) > Comment on attachment 421136 [details] > Patch > > If the test elements contained one glyph each, what would happen? FCP will be marked the moment one of them become visible, and from that point on the check wouldn't run (as it only measures the *first* contentful paint).
EWS
Comment 4 2021-02-21 11:07:38 PST
Committed r273220: <https://commits.webkit.org/r273220> All reviewed patches have been landed. Closing bug and clearing flags on attachment 421136 [details].
Radar WebKit Bug Importer
Comment 5 2021-02-21 11:08:14 PST
Note You need to log in before you can comment on or make changes to this bug.