You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See the DynamicPage header is still interactive when loading
Log Output, Stack Trace or Screenshots
No response
Priority
High
UI5 Web Components Version
2.5.0
Browser
Chrome
Operating System
MacOS
Additional Context
When the whole page is loading, interactive page header is not expected. Because in some cases the loading is triggered from the page header, if user clicks on the page header elements during loading would duplicate the loading action and cause performance or other potential issue.
Organization
SAP SuccessFactors
Declaration
I’m not disclosing any internal or sensitive information.
The text was updated successfully, but these errors were encountered:
Hi @ilhan007
Many thanks for your quick support and this workaround looks good. And we also want to confirm will @ui5/webcomponents provide internal fix in the future? Or the current z-index for the DynamicPage header is expected behavior?
Bug Description
When DynamicPage is wrapped in ui5-busy-indicator, the header area can still be interactive when busy status set to active.
Affected Component
ui5-dynamic-page
Expected Behaviour
DynamicPage header area should not be interactive when wrapped in active busy indicator.
Isolated Example
https://stackblitz.com/edit/github-gafhlvhg?file=src%2FApp.tsx
Steps to Reproduce
Log Output, Stack Trace or Screenshots
No response
Priority
High
UI5 Web Components Version
2.5.0
Browser
Chrome
Operating System
MacOS
Additional Context
When the whole page is loading, interactive page header is not expected. Because in some cases the loading is triggered from the page header, if user clicks on the page header elements during loading would duplicate the loading action and cause performance or other potential issue.
Organization
SAP SuccessFactors
Declaration
The text was updated successfully, but these errors were encountered: