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
useAnimation ignores certain style declarations on browsers that don't support WebAnimations #25635
Comments
Alright I finally got to look at this. Turns out that The fix here should be that the angular animation code should place |
…utside of keyframes/web-animations When web-animations and/or CSS keyframes are used for animations certain CSS style values (such as `display` and `position`) may be ignored by a keyframe-based animation. Angular should special-case these styles to ensure that they get applied as inline styles throughout the duration of the animation. Closes angular#24923 Closes angular#25635 Jira Issue: FW-1091 Jira Issue: FW-1092
…utside of keyframes/web-animations When web-animations and/or CSS keyframes are used for animations certain CSS style values (such as `display` and `position`) may be ignored by a keyframe-based animation. Angular should special-case these styles to ensure that they get applied as inline styles throughout the duration of the animation. Closes angular#24923 Closes angular#25635 Jira Issue: FW-1091 Jira Issue: FW-1092
…utside of keyframes/web-animations When web-animations and/or CSS keyframes are used for animations certain CSS style values (such as `display` and `position`) may be ignored by a keyframe-based animation. Angular should special-case these styles to ensure that they get applied as inline styles throughout the duration of the animation. Closes angular#24923 Closes angular#25635 Jira Issue: FW-1091 Jira Issue: FW-1092
…utside of keyframes/web-animations When web-animations and/or CSS keyframes are used for animations certain CSS style values (such as `display` and `position`) may be ignored by a keyframe-based animation. Angular should special-case these styles to ensure that they get applied as inline styles throughout the duration of the animation. Closes angular#24923 Closes angular#25635 Jira Issue: FW-1091 Jira Issue: FW-1092
…utside of keyframes/web-animations When web-animations and/or CSS keyframes are used for animations certain CSS style values (such as `display` and `position`) may be ignored by a keyframe-based animation. Angular should special-case these styles to ensure that they get applied as inline styles throughout the duration of the animation. Closes angular#24923 Closes angular#25635 Jira Issue: FW-1091 Jira Issue: FW-1092
…utside of keyframes/web-animations When web-animations and/or CSS keyframes are used for animations certain CSS style values (such as `display` and `position`) may be ignored by a keyframe-based animation. Angular should special-case these styles to ensure that they get applied as inline styles throughout the duration of the animation. Closes angular#24923 Closes angular#25635 Jira Issue: FW-1091 Jira Issue: FW-1092
…utside of keyframes/web-animations (#28911) When web-animations and/or CSS keyframes are used for animations certain CSS style values (such as `display` and `position`) may be ignored by a keyframe-based animation. Angular should special-case these styles to ensure that they get applied as inline styles throughout the duration of the animation. Closes #24923 Closes #25635 Jira Issue: FW-1091 Jira Issue: FW-1092 PR Close #28911
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
I'm submitting a...
Current behavior
Certain style definitions (like 'position', 'top', 'right' etc could be others as well) in reusable animations are ignored on browsers that don't support WebAnimations. This used to work fine in Angular 5 and earlier where the web animation polyfill was used. Interestingly, they work fine if defined directly on the transition - in a non reusable manner.
Expected behavior
Styles in reusable animations should work fine in all browsers, as it used to in Angular 5 and earlier.
Minimal reproduction of the problem with instructions
position
andright
properties in Chrome.What is the motivation / use case for changing the behavior?
To be able use reusable animations properly regardless of the browser.
Environment
The text was updated successfully, but these errors were encountered: