Skip to content
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

Merged
merged 1 commit into from
Mar 3, 2023

Conversation

fantasai
Copy link
Collaborator

@fantasai fantasai commented Mar 3, 2023

No description provided.

@fantasai fantasai requested a review from dbaron March 3, 2023 03:32
Copy link
Member

@dbaron dbaron left a 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.

css-transitions-2/Overview.bs Outdated Show resolved Hide resolved
css-transitions-2/Overview.bs Show resolved Hide resolved
css-transitions-2/Overview.bs Outdated Show resolved Hide resolved
@fantasai
Copy link
Collaborator Author

fantasai commented Mar 3, 2023

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'm patching the definition of "transitionable" here; I don't see that, with that change, anything in "Starting of transitions" needs edits?

@dbaron
Copy link
Member

dbaron commented Mar 3, 2023

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 all is specified for transition-property, which is incorrect.

@fantasai
Copy link
Collaborator Author

fantasai commented Mar 3, 2023

With your patch to "transitionable", the detailed algorithm in "Starting of transitions" will start transitions for discretely-animatable properties when all is specified for transition-property, which is incorrect.

I don't see where it says that. It doesn't mention the all keyword in that section at all, afaict. And the section we're editing here now says very clearly that discretely-animatable properties are not included in all. So I don't see how you're arriving at this conclusion.

@dbaron
Copy link
Member

dbaron commented Mar 3, 2023

I don't see where it says that. It doesn't mention the all keyword in that section at all, afaict. And the section we're editing here now says very clearly that discretely-animatable properties are not included in all. So I don't see how you're arriving at this conclusion.

OK, after rereading, I agree.

Copy link
Member

@dbaron dbaron left a 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.

@dholbert
Copy link
Member

I have an editorial nit with the new text here which I filed as #8761

@dholbert
Copy link
Member

dholbert commented May 5, 2023

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?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants