- Should it check for elements which are paintable? According to current specs it says
https://www.w3.org/TR/paint-timing/#mark-paint-timing
5.3.2 Mark paint timing
.
.
.
10.
- If reportedPaints does not contain "first-paint"... then report paint timing given document, "first-paint"”
- What are the exceptions that need to be considered with non-default background? When its opacity is 0, should it be reported?
Observation in Chrome
TC1: data:text/html, <html style="background: yellow; opacity: 0">
FP: Yes.
With opacity: 0, it is the same as the default background. Still we see Fp on Chrome
TC2: data:text/html, <body style="opacity: 0">foo
FP: No
Acc to specs, we create a paintedtextNode. And we reach step 10, and should report first-paint
TC3: data:text/html, <div style="height: 100px; background: yellow; opacity: 0">
FP: Same as TC2
Proposed Behavior:
It should check if the element is paintable and then mark first-paint.
https://www.w3.org/TR/paint-timing/#mark-paint-timing
Observation in Chrome
TC1:
data:text/html, <html style="background: yellow; opacity: 0">FP: Yes.
With opacity: 0, it is the same as the default background. Still we see Fp on Chrome
TC2:
data:text/html, <body style="opacity: 0">fooFP: No
Acc to specs, we create a paintedtextNode. And we reach step 10, and should report first-paint
TC3:
data:text/html, <div style="height: 100px; background: yellow; opacity: 0">FP: Same as TC2
Proposed Behavior:
It should check if the element is paintable and then mark first-paint.