On Fri, Jan 10, 2020 at 9:41 AM Ingo Schwarze <[email protected]> wrote: > > > I found out that Apple requires nonstandard [1] attributes to fully > > "fix" this. I don't know if using nonstandard attributes is the right > > way to go, but Apple, Google, and DuckDuckGo are using these attributes > > on their search fields. > > > > According to Apple's own documentation, the "autocapitalize" attribute > > really should be set to "none," but all three of the previously > > mentioned sites use the deprecated "off" value instead. I assume they > > know something I don't with regards to compatibility. > > The "autocapitalize" attribute is actually a standard attribute. > The autocapitalize feature makes no sense in general, and even less > so for this form, but the standard says it is half-on by default, > so i committed autocapitalize=\"none\" to switch it off.
Ah, you're right about autocapitalize. I should have checked the latest spec rather than relying on MDN. Thanks for pointing that out. > The "autocorrect" attribute indeed doesn't exist, and i refuse > knowingly violating the standards, unless in exceptional cases when > standards are being particularly stupid. Not defining "autocorrect" > is certainly not a bug in the standard - quite to the contrary, web > standard are sprawling already and define lots of stuff they shouldn't. > > Violating the standards in order to cater to individual vendors > also violating the standards is evil because it help vendors who > deploy vendor-lockin strategies. Conversely, users using software > violating the standards deserve to be punished. Maybe they might > switch to software better respecting the standards, if that exists. > Either way, that's the only way to motivate vendors to abandon > lockin strategies and implement standards instead. I think most people can live without the autocorrect attribute since the auto-capitalization part is by far the worse evil of the two. You typically don't notice it until you're at the end of whatever you're typing and have to awkwardly get back to the beginning of the input field and awkwardly fix it. > Again, the committed patch shown below is installed on man.openbsd.org > such that people can test if they want. Thank you for getting these changes in and so quickly. I will no longer get as agitated when I'm looking at man pages away from my desk. :) Tim
