-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify: are gradients considered contentful? #61
Comments
I tend to agree that gradients are not very contentful (given that colors aren't). I did a quick test, Chrome currently does consider them as contentful. But I'm open to changing it, and we can mention this in the spec either way. |
Related, we really need to more rigorously define what it means for an image to be rendered, or even what an image means in this context. For example, [https://drafts.csswg.org/css-images-4/#image-values]( type) defines the CSS syntax for specifying images in places like And then for each one of those properties, we need to define under what condition a specified image is considered as rendered. For example, A border image with All these things need to precisely defined. |
I tried to address this here: #66 |
I believe that #66 addresses this, closing. |
@noamr so they will not be considered contentful, correct? Once you confirm I can add a test (Chrome will fail it at the moment). |
Correct. Only loaded images will be considered contentful. |
Please don't close an issue until the relevant PR is landed. It's very confusing. |
OK, sorry :) |
Closing now that the PR is landed. https://w3c.github.io/paint-timing/ |
Currently according to the spec, background images are considered contentful in terms of measuring FCP. The definition of images in CSS also includes gradients. I'm not sure they should be - they're more similar to background colors than they are to images in terms of what "content" is - but in any case the spec should maybe clarify this.
The text was updated successfully, but these errors were encountered: