Conversation
8b0dfee to
e3503d2
Compare
|
Is there a specific reason we want to focus the refresh button initially? The first focusable element would rather be the first button in the toolbar. However from usability perspective it'd make more sense to focus the big "New Container" button, users who don't have created any container yet, can just proceed from there and others need only to hit Tab once to reach their data. Thoughts? |
As per your suggestion it will make more sense; However, the ticket specifies that the focus should be on the refresh button when opening the Data Explorer. |
I agree with Sevo. Let's seek clarification from the accessibility team. |
|
There is a new comment that they closed the bug which is unfortunate. Let's just go ahead and focus the "New Container" button as we discussed? |
…pens after activating "Data Explorer" menu item present under 'Overview' page.
e3503d2 to
0f31554
Compare
Sure @sevoku, I’ve discussed this with the accessibility team, but I haven’t received any feedback from them yet. Let’s go ahead with your suggestion for the "New Container" button, as it looks good from every angle. |
This PR addresses an issue where keyboard focus is lost when navigating to the Data Explorer page from the Overview page in Azure Cosmos DB. The problem was that after activating the "Data Explorer" menu item, the page did not correctly set focus on the expected element, impairing keyboard navigation.
Note: We are Using
setTimeoutwith0msensures that the code runs asynchronously after the current execution context completes. Without it, the code is not working as expected due to JavaScript's synchronous execution model.Preview this branch
accessibility-1217621.mp4