-
Notifications
You must be signed in to change notification settings - Fork 383
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
[AMP Stories] Animation Order #1904
Conversation
I'm gonna implement a data store as provided by This is gonna be needed for future UI iterations anyway, see #1882 (comment) for example, where animation order is displayed in a central place. Upon editor initialization, I'd go through all existing blocks to determine the order and set the default state. |
The two main things left to do:
|
Cycle prevention is fixed now. Example: When block A is set to start after B, one cannot select B to start after A. Nothing happens when you try to click on such an invalid option. To further improve messaging to the user, we could think about hiding or disabling invalid choices in the picker. Perhaps with a detailed explanation below the control or something. |
@swissspidy One additional note about the PR from functional testing: |
Interesting. So a block was shown in the dropdown that actually wasn't animated? Or did you add the animation to both and then removed it from the first (which then didn't update the other one)? |
The block was shown in the dropdown what wasn't actually animated. |
To do:
<Dropdown>
component like we already do in [AMP Stories] Font Selection #1885 so we can show each block with its block type's icon.animatedBlocks
update.Right now, content changes aren't reflected in the drop downs.
onChange
, go through all animated blocks to ensure there are no cycles. ** Similar checks might be needed when removing blocks. This begs the question whether it makes sense to store animation order in list instead of just having each animated block reference its predecessor.
See #1882