Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
I'm looking at the behaviour of Chrome and my test framework and trying to understand what the correct behaviour should be before raising an issue/ticket on one or the other (or revisiting how my t...
#2: Post edited
by
Alexei
·
2023-08-05T20:40:22Z (over 1 year ago)
added tags
#1: Initial revision
by
pureferret
·
2023-08-05T15:21:49Z (over 1 year ago)
What does the w3c standard say about tabbing away from a disabled element?
I'm looking at the behaviour of Chrome and my test framework and trying to understand what the correct behaviour should be before raising an issue/ticket on one or the other (or revisiting how my test works). The test/user operation is to tab onto a button, press enter and as a side effect that button with focus becomes disabled. Then the user tabs away from that button to one that's adjacent in the DOM. There's a working example in a question I asked on StackOverflow [here](https://stackoverflow.com/questions/76773916/tabbing-off-a-recently-disabled-element-with-a-react-testing-library-does-not-co). What happens in the browser is that the focus switches to the adjacent button. But in the test, the focus switches back to the first navigable/focusable element inside the disabled element's parent element. I've looked though various parts of the [standard](https://html.spec.whatwg.org/multipage/interaction.html#focus) but I'm either missing it (it's quite a dry read!) or that behaviour isn't defined? What is meant to happen when tabbing away from a disabled element?