-
Notifications
You must be signed in to change notification settings - Fork 647
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
[css-contain-4] Make content-visibility animatable #8627
Comments
|
My simple proposal would be that |
@flackr can you put a bit more detail into your proposal? I am not entirely sure how to summarize the above for an async resolution. |
The three main points are:
|
Thanks for explaining further. This seems like a good thing to get in the spec for more review. The CSSWG will automatically accept this resolution one week from now if no objections are raised here. Anyone can add an emoji to this comment to express support. If you do not support this resolution, please add a new comment. Proposed Resolution: Make content-visibility animateable as above |
RESOLVED: Make content-visibility animateable as above |
Allow animating content-visibility as animation type discrete with special interpolation to avoid hidden values similar to visibility. Fixes w3c#8627
Allow animating content-visibility as animation type discrete with special interpolation to avoid hidden values similar to visibility. Fixes #8627.
css-contain Section 4 currently defines the content visibility property to be Animation type: not animatable. Most likely this was done for simplicity since like display it can affect which animations are running. However, as with display where we are better refining the ways in which it is safe to animate (See #6429), we should figure out in which ways content-visibility can be animated.
In particular, just like display it should be possible for an animation to extend the application of
content-visibility: visible
in order to allow content to stay visible while an animation is completing. This would be useful for elements like<details>
whose contents arecontent-visibility: hidden
when closed.The text was updated successfully, but these errors were encountered: