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
I understand this is a bug report and questions should be posted in the Community Forum
I searched issues and couldn’t find anything (or linked relevant results below)
Link to runnable example
No response
Steps to reproduce
Just use uppy normally with dashboard, no special setup needed
Expected behavior
No errors from chrome.
This seems like a new chrome validation. The status bar is using aria-hidden property to block focus, and it shouldn't.
Actual behavior
Chrome console gives this error:
Blocked aria-hidden on an element because its descendant retained focus. The focus must not be hidden from assistive technology users. Avoid using aria-hidden on a focused element or its ancestor. Consider using the inert attribute instead, which will also prevent focus. For more details, see the aria-hidden section of the WAI-ARIA specification at https://w3c.github.io/aria/#aria-hidden.
Element with focus: button
Ancestor with aria-hidden: <div class="uppy-StatusBar is-complete" aria-hidden="true">…</div>
The text was updated successfully, but these errors were encountered:
Initial checklist
Link to runnable example
No response
Steps to reproduce
Just use uppy normally with dashboard, no special setup needed
Expected behavior
No errors from chrome.
This seems like a new chrome validation. The status bar is using aria-hidden property to block focus, and it shouldn't.
Actual behavior
Chrome console gives this error:
The text was updated successfully, but these errors were encountered: