[Webkit-unassigned] [Bug 22261] Clicking on a non-text input element does not give it focus

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Jun 13 14:46:32 PDT 2021


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

--- Comment #79 from John A. Bilicki III <jab_creations at yahoo.com> ---
>> the user agent might determine that an element is not click focusable even if it is focusable. For example, in some user agents, clicking on a non-editable form control does not focus it, i.e. the user agent has determined that such controls are not click focusable

>So the behavior of Safari on Mac in this case is perfectly fine, and standards-compliant.

Those are elements with the disabled attribute or are hidden by elements with greater z-index layers.

>not a big fan of requiring authors to once again add extra markup/putting the onus on them to fix sites to accommodate for an idiosyncratic quirk of one particular user agent...

The more quirks we have to deal with the less time we get to spend with our families or on non-work related activities.

>Generally speaking, when reading a spec, "SHOULD" means recommended but not required. 

The point of having a specification or standard is to ELIMINATE the quirks between browsers; the word "SHOULD" has ZERO justification to be in any specification or standard. When someone argues "but..." then THEY are required to distinguish scenarios one and two and clarify any other scenarios requiring clarification.

I've personally encountered alarming amounts of incompetence in "standards" such as scrollbar-width. The entire Git conversation was monopolized by people arguing over literal absolute ambiguities. The word 'thin' has zero absolute definition, it was useless because obviously what a Linux die-hard think is "thin" will differ from a Windows die-hard's version of "thin". Therefore the "standard" is pseudo (not really) because it "officialized" ambiguity and ruins forward-compatibility. Therefore when work on my own browser engine begins my team will adhere to proper standards and ignore anything ambiguous. Will people be upset? Yes, though they aren't the ones stuck working until 4AM dealing with who have to be awake to help their families at 8AM.

I understand why there is a lot of animosity towards behavior associated with Microsoft products however a good idea is a good idea period. If Mao, Hitler or Stalin say 2 + 2 = 4 and then further clarify that they are explicitly using the decimal system (versus 1 + 1 (spoken) = three and not clarifying binary) the fact that those were absolute evil marxist dictators does not change the fact that the sentence they spoke is true. At the end of the day work on browser engines is either done in the context of helping humans or enforcing some arbitrary notion because of some completely unrelated hatred. Competence and good behavior of a rendering engine is in absolute more important in the context of helping your fellow human beings.

-- 
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/20210613/7bb30f2e/attachment.htm>


More information about the webkit-unassigned mailing list