On Tue, May 12, 2020 at 1:36 AM Maciej Stachowiak <mjs@apple.com> wrote:

I noticed from comments in one of the Radars that the patch may result in an additional “fake paint”, so it should probably be performance tested. Have you done any testing?
I've tested it locally, I haven't noticed any significant side effect, because in complex situations the fake paint only happens once per page and bails early once contentfulness is detected. but I can run any additional test needed.
 
We’ll likely want to A/B some of Apple’s page load speed benchmarks.
A/B testing load speed sounds sensible. How do we go about doing that?
 

I’d like to hear from others on maturity of the spec and readiness of the code.

 - Maciej

On May 11, 2020, at 11:44 AM, Noam Rosenthal <noam@webkit.org> wrote:

Following the discussion with Simon in https://bugs.webkit.org/show_bug.cgi?id=78011

Since we have a pretty stable spec (https://w3c.github.io/paint-timing/), lots of passing web platform tests, other browser vendor support and a working implementation of first contentful paint, I am planning to submit a patch to enable paint timing by default. 

Any objections? Other thoughts?
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev