Nothing Special   »   [go: up one dir, main page]

Bug 1805727 Comment 1 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Clarifying slightly:

Up until this point, the spec has said the following:
> When comparing the before-change style and after-change style for a given property, the property values are transitionable if they have an animation type that is neither `not animatable` nor `discrete`.

The change here is:
* we're removing the "...nor discrete" qualifier. So: now properties with animation-type "disrete" *are* considered to be transitionable
* they transition when their easing function gets past 50%, essentially (this falls implicitly out of the animation spec and how it interacts with transitions)
* discretely-transitionable properties **are not included** in `transition-property: all`.  If you want to transition them, you have to explicitly list them by name in the `transition-property` list.

(There's a proposal to include another catch-all keyword for all such properties so that you could do something like `transition-property: all, discrete`, but we didn't resolve on that today.)
Clarifying slightly:

Up until this point, the spec has said the following (in [section 3 "Starting of transitions"](https://www.w3.org/TR/css-transitions-1/#starting)):
> When comparing the before-change style and after-change style for a given property, the property values are transitionable if they have an animation type that is neither `not animatable` nor `discrete`.

The change here is:
* we're removing the "...nor discrete" qualifier. So: now properties with animation-type "disrete" *are* considered to be transitionable
* they transition when their easing function gets past 50%, essentially (this falls implicitly out of the animation spec and how it interacts with transitions)
* discretely-transitionable properties **are not included** in `transition-property: all`.  If you want to transition them, you have to explicitly list them by name in the `transition-property` list.

(There's a proposal to include another catch-all keyword for all such properties so that you could do something like `transition-property: all, discrete`, but we didn't resolve on that today.)
Clarifying slightly:

Up until this point, the spec has said the following (in [section 3 "Starting of transitions"](https://www.w3.org/TR/css-transitions-1/#starting)):
> When comparing the before-change style and after-change style for a given property, the property values are transitionable if they have an animation type that is neither `not animatable` nor `discrete`.

Today's resolution made this change:
* we're removing the "...nor discrete" qualifier. So: now properties with animation-type "disrete" *are* considered to be transitionable
* they transition when their easing function gets past 50%, essentially (this falls implicitly out of the animation spec and how it interacts with transitions)
* discretely-transitionable properties **are not included** in `transition-property: all`.  If you want to transition them, you have to explicitly list them by name in the `transition-property` list.

(There's a proposal to include another catch-all keyword for all such properties so that you could do something like `transition-property: all, discrete`, but we didn't resolve on that today.)

Back to Bug 1805727 Comment 1