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 }}
Repository navigation
Support transition-behaviour for display and content-visibility #1384
Reacted by John P. Green, Nilesh Prajapati, Christopher Kirk-Nielsen, phantomxx29474, Valtteri Laitinen, Michael, thaddeusleaf-spec, dsenneff, Alexander Lehner, Jayden Pearse and 35 more
This comment was automatically generated based on the information you provided. Please don't edit it.
Below is additional information about the web feature (from the web-features project) which is referenced in your proposal.
If this doesn't accurately correspond to your proposal, please update your initial comment to include web-features: <feature-id>.
To find feature IDs, use the web-features explorer.
Feature display animation
ID: display-animation
Name: display animation
Description: You can animate elements between display: none and any other display value or animate between content-visibility: hidden and any other content-visibility value. This also applies to transitions.
So the other related issue (#1456) was clear that the overlay property is explicitly not covered, but this issue is less clear. Can we be explicit that this issue does not cover the overlay property?
We should also include the overlay property as well.
According to the Deprecate and remove: CSS overlay property chromestatus entry, developer feedback about the overlay property has shown that it creates bugs that are hard to track down, and Chrome engineers want to deprecate the property and keep the animated elements in the top layer automatically during their exit animations.
I agree with @mfreed7 that this proposal should exclude the overlay property, and only focus on animating display and content-visibility, which is the final platform gap that will make top layer elements, like elements, or elements with the popover attribute, animatable as they enter and exit the top layer.
Reacted by phantomxx29474, John and João Beleza Freire
Activity
github-actions commentedon Sep 9, 2026
This comment was automatically generated based on the information you provided. Please don't edit it.
Below is additional information about the web feature (from the web-features project) which is referenced in your proposal.
If this doesn't accurately correspond to your proposal, please update your initial comment to include
web-features: <feature-id>.To find feature IDs, use the web-features explorer.
Feature display animation
display: noneand any otherdisplayvalue or animate betweencontent-visibility: hiddenand any othercontent-visibilityvalue. This also applies to transitions.displayCSS property,content-visibilityCSS propertyphantomxx29474 commentedon Sep 9, 2026
Firefox have been working on a prototype for animating display and content-visibility animations in their group.
Source: https://groups.google.com/a/mozilla.org/g/dev-platform/c/VPL2DbXUu7c
mfreed7 commentedon Oct 2, 2026
So the other related issue (#1456) was clear that the
overlayproperty is explicitly not covered, but this issue is less clear. Can we be explicit that this issue does not cover theoverlayproperty?phantomxx29474 commentedon Oct 3, 2026
We should also include the overlay property as well.
captainbrosset commentedon Oct 5, 2026
According to the Deprecate and remove: CSS overlay property chromestatus entry, developer feedback about the overlay property has shown that it creates bugs that are hard to track down, and Chrome engineers want to deprecate the property and keep the animated elements in the top layer automatically during their exit animations.
I agree with @mfreed7 that this proposal should exclude the
overlayproperty, and only focus on animatingdisplayandcontent-visibility, which is the final platform gap that will make top layer elements, like elements, or elements with the popover attribute, animatable as they enter and exit the top layer.