Implement :focus-within from Selectors 4
Tons of UIs include elements that are not visible unless the user interacts with their parent or ancestor. Think popup menus, delete or edit buttons, floating formatting toolbars, copy buttons, editing popups and so on. The list is endless. This is a good way to reduce visual clutter.
Selectors 4 fixes this by introducing :focus-within, which will work just like :hover in the sense that it will also apply to ancestors. This will make it trivial to make the UIs described above keyboard accessible.
Why is this still missing?!
Derek Jordan commented
Accessibility is an imperative in web development, and has been for at least 2 years already. Why is IE still missing this?
What is "Edge" the edge of, exactly? Does "edge" refer to the remote reaches of established web development where the denizens are still relying on dialup?
Please incorporate. It's not discomfort coding with js but rather the idea that users disable js for their own reasons and a website should not sacrifice accessibility in those cases.
L. Reece commented
We need this to be able to make focusable items WITHIN hidden areas keyboard accessible (by keeping the hidden area from dropping off when losing focus by going inside it). This is a no-brainer. This should've been implemented YEARS ago.
+1 this is absolutely a top priority for accessible forms.
Brandon Brown commented
Ya, this is huge for Accessibility when you need to make overlays accessible on keyboard focus and not just hover.
Finally, it has a status page:
Thomas Darling commented
Just get this done already!
The suggestion for this much needed feature has been sitting here for 2 years now, every other major browser supports it, and it's not even on your backlog yet...
You really need to allocate more resources to all those little features we all need, instead of focussing so much on the big ones that take forever to deliver.
Mike herchel commented
Azure Dan commented
This feature would be very helpful in implementing accessibility within the browser
Bill G commented
Why doesn't Edge have this yet? We need this, it's a no-brainer!
Edge is the last one missing in almost all amazing new features.
Why don't you just kill Edge and left the people choose a browser in Windows and sites will be easier for developer and faster and more beautiful for users.
Michael Maaß commented
We are all just temporarily not disabled.
Hurry the F-up!
Jiří Thiemel commented
Really important one. Plus the whole logic of this is so simple it can be described in one sentence (even in the spec). There is nothing to discuss and should be easy to implement without any worries. I understand that implementing web components and similar things takes a lot of time. But this is a different story.
S. M. Abdul Aziz commented
it should have in Edge 17, frustrated to not have it in this modern version of edge.. 😒😒
Dean Ashworth commented
This is a no brainer for A11y.
Shout out to Una!... https://css-tricks.com/solved-with-css-dropdown-menus/