-
Notifications
You must be signed in to change notification settings - Fork 669
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-transitions-1] Make discrete properties transition at 50%; exclude them from 'all'. #4441 #8520
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is mostly good, although there are a number of things that are awkward about doing this as a delta spec and it's not completely clear how diff-like to make some of the edits.
I have a few comments below.
In addition to those comments, I think you should specifically patch all occurences of "transitionable" in the "Starting of transitions" section, which does need to be patched to make this part of the detailed algorithm. I think that may need a term (I have mixed feelings about whether to re-use "transitionable") that considers whether the relevant part of transition-property
was all
or not.
468fa68
to
c48cd62
Compare
I'm patching the definition of "transitionable" here; I don't see that, with that change, anything in "Starting of transitions" needs edits? |
With your patch to "transitionable", the detailed algorithm in "Starting of transitions" will start transitions for discretely-animatable properties when |
I don't see where it says that. It doesn't mention the |
…de them from 'all'. See w3c#4441
c48cd62
to
c109e1b
Compare
OK, after rereading, I agree. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, looks good. Thanks.
I have an editorial nit with the new text here which I filed as #8761 |
I also have one question about various tests that were updated to test this change but I think are mistaken; see web-platform-tests/wpt#39871 (Alternately, maybe the tests are right and the spec-text just needs clarification?) |
No description provided.