[Webkit-unassigned] [Bug 26856] AnchorElement, ButtonElement, InputButton and Document should fire focus event when it is clicked.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=26856

Kyle Simpson <getify at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |getify at gmail.com

--- Comment #48 from Kyle Simpson <getify at gmail.com> ---
Is there a plan to revive this bug and finally address it? I ask because the bug I was part of (about radio buttons) was just marked as a dupe and merged into this one, but here this bug appears dormant for 11 years.

Also, reading this thread, I find it unusual that the original objection was that elements which are focused "look bad" if there is some visual indication they are focused. I'm fairly certain that A11Y guidelines strongly push for elements which are focused to be visually obvious that they are focused. The fact that someone doesn't like what it looks like for a link or radio button to be focused is a CSS styling question, not a functionality question.

When devs remove the `outline` on a focused element (probably at the request of some client or designer) and don't replace it with some other visual indication -- I prefer using an inner box shadow to make an element sort of "glow" -- that omission is pretty universally considered a bad A11Y practice, as far as I can tell.

----

I had long since forgotten that back in 2012 I was participating in that other bug about focus not working on radio buttons, and was only reminded when I saw the email indicating the dupe/merge here.

But I fairly recently had this same problem in a PWA I built.

I created a click handler for all buttons, checkboxes, and radio buttons in my app, that forces the element to be focused, so that mouse clicks or taps cause my CSS :focus styling to be applied in safari the same as it was automatically being applied in other browsers/platforms.

So yeah, this is STILL a bug that code is still having to work-around.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210521/23863a54/attachment-0001.htm>