You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
The explainer for renderpriority suggests that the use case is to prepare content which was hidden to be displayed. I'd like to suggest that we consider using will-change: content-visibility as a hint for this. will-change is an already established rendering hint which is currently used to tell the UA to prepare for elements to have mutations to transforms, opacity, etc, so it seems reasonable that will-change: content-visibility could be used as a hint for the UA to prepare for changes to content-visibility (i.e. update the rendering of the element).
The text was updated successfully, but these errors were encountered:
The explainer for renderpriority suggests that the use case is to prepare content which was hidden to be displayed. I'd like to suggest that we consider using
will-change: content-visibility
as a hint for this. will-change is an already established rendering hint which is currently used to tell the UA to prepare for elements to have mutations to transforms, opacity, etc, so it seems reasonable thatwill-change: content-visibility
could be used as a hint for the UA to prepare for changes to content-visibility (i.e. update the rendering of the element).The text was updated successfully, but these errors were encountered: