We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Page animation are still displayed even if animationMode configuration is set to none
https://sap.github.io/ui5-webcomponents/nightly/packages/fiori/test/pages/Page.html?sap-ui-animationMode=none
https://sap.github.io/ui5-webcomponents/nightly/packages/main/test/pages/ProgressIndicator.html?sap-ui-animationMode=none
No response
I would expect animation to not exist
...
None
nightly
Chrome
The text was updated successfully, but these errors were encountered:
Hello @SAP/ui5-webcomponents-topic-rl ,
The issue is reproducible with the sample provided. The animation is applied in the Page.css file.
Kind Regards, Elena
Sorry, something went wrong.
fix(ui5-page): fix double footer and adjust animation timing
350f552
FIXES: #9755 FIXES: #9756
e8beb76
fix(ui5-page): fix double footer and adjust animation timing (#9885)
e901877
MapTo0
Successfully merging a pull request may close this issue.
Bug Description
Page animation are still displayed even if animationMode configuration is set to none
https://sap.github.io/ui5-webcomponents/nightly/packages/fiori/test/pages/Page.html?sap-ui-animationMode=none
https://sap.github.io/ui5-webcomponents/nightly/packages/main/test/pages/ProgressIndicator.html?sap-ui-animationMode=none
Affected Component
No response
Expected Behaviour
I would expect animation to not exist
Isolated Example
No response
Steps to Reproduce
...
Log Output, Stack Trace or Screenshots
No response
Priority
None
UI5 Web Components Version
nightly
Browser
Chrome
Operating System
No response
Additional Context
No response
Organization
No response
Declaration
The text was updated successfully, but these errors were encountered: