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
When rendering an ui5-dialog for the first time and immediately opening it with an active ui5-busy-indicator inside, the site crashes with a JS runtime error:
TypeError: Cannot read properties of null (reading 'focus')
Expected Behavior
Busy Indicator should be active and no error should be thrown
- Don't render focusable elements until the delay has passed
- Don't reduce the opacity and prevent actions of the slotted elements until the delay has passed
Fixes: #4108
Don't render focusable elements until the delay has passed
Don't reduce the opacity and prevent actions of the slotted elements until the delay has passed
Fixes: #4108
Don't render focusable elements until the delay has passed
Don't reduce the opacity and prevent actions of the slotted elements until the delay has passed
Fixes: SAP#4108
Bug Description
When rendering an
ui5-dialog
for the first time and immediately opening it with an activeui5-busy-indicator
inside, the site crashes with a JS runtime error:Expected Behavior
Busy Indicator should be active and no error should be thrown
Steps to Reproduce
Isolated Example
https://codesandbox.io/s/table-dialog-busy-ntti7?file=/src/App.js
Context
ui5-busy-indicator
Log Output / Stack Trace / Screenshots
Priority
The priority indicates the severity of the issue. To set the appropriate priority consider the following criteria:
Note: The priority might be re-evaluated by the issue processor.
Stakeholder Info (if applicable)
The text was updated successfully, but these errors were encountered: