- Issue created by @rkoller
- Assigned to bronzehedwick
- Merge request !218Issue #3437375: Allow only one submenu to be open at a time β (Open) created by bronzehedwick
- Issue was unassigned.
- Status changed to Needs review
8 months ago 4:30pm 1 April 2024 - π©πͺGermany rkoller NΓΌrnberg, Germany
thank you for the quick fix, I've manually tested and and can confirm the behavior is as expected now. i've tested on the configuration menu and only one submenu remains open at a time.
i've only noticed one detail i am unsure if it is possible to be fixed. if you are having voiceover active then the voiceover cursor position remains at the position the submenu item was before it got expanded. so you have the voiceover cursor and the focus outline in two different places. - πΊπΈUnited States bronzehedwick New York
Great catch @rkoller! We can move the focus using JavaScript. I'll work on that now.
- Assigned to bronzehedwick
- Status changed to Active
8 months ago 4:51pm 1 April 2024 - πΊπΈUnited States bronzehedwick New York
Hey @rkoller, I tested the VO/keyboard focus with the built-in macOS accessibility tools using Firefox, and wasn't able to replicate the issue.
vo-keyboard-focus-in-sync.mov β
Is there a step to reproducing I'm missing?
- Status changed to Postponed
8 months ago 5:07pm 2 April 2024 - πͺπΈSpain ckrina Barcelona
Based on Slack conversation postponing this until π Drawer closes when moving from the opening item to "popover" Needs review gets in. Let's see if this is still needed when that gets in.
- Status changed to Fixed
8 months ago 12:03pm 3 April 2024 - πͺπΈSpain ckrina Barcelona
This has been fixed in π Drawer closes when moving from the opening item to "popover" Needs review . Closing as fixed per the work done here :)
- π©πͺGermany rkoller NΓΌrnberg, Germany
@ckrina the problem with the focus and VO-cursor still persists. in safari they remain separated as long as no new keyboard input happens while in edge and firefox there is the short delay as described in the conversation on slack by @bronzehedwick. i still have to do some research (asking on the a11y slack and or safari folks on mastodon), should i open up a followup issue as soon as i get news or should i already open up a one outlining the problem in case someone else comes along knowing how to fix this?
Automatically closed - issue fixed for 2 weeks with no activity.