Re:Issue 914451: Autofill does not respect autocomplete="off"
by nikanj on Sunday October 13, 2019 @04:55AM
(#21239307)
The spec only says "should", not "must". Apparently these wingnuts thought that means the spec can be ignored.
[ Parent
| on HN ]
Re:Issue 914451: Autofill does not respect autocomplete="off"
by reificator on Sunday October 13, 2019 @05:08AM
(#21239347)
> The spec only says "should", not "must". Apparently these wingnuts thought that means the spec can be ignored.
Not arguing in favor of this particular choice, but yes. That is exactly what "should" means in most cases.
For instance, in RFC 2119: https://tools.ietf.org/html/rfc2119
> SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.
Re:Issue 914451: Autofill does not respect autocomplete="off"
by azernik on Sunday October 13, 2019 @02:48PM
(#21242075)
Blanket disregard of a SHOULD directive as a UX decision neither falls under "in particular circumstances" nor indicates that they've "understood and carefully weighed" the consequences.
Re:Issue 914451: Autofill does not respect autocomplete="off"
by ko27 on Sunday October 13, 2019 @05:08AM
(#21239349)
There are no semantics to discuss. Chrome is spec compliant. That's a fact. Words like "should" and "must" have well defined meaning that is clarified in every spec document, which I would highly advise you to read before writing any further comments and insults.
Re:Issue 914451: Autofill does not respect autocomplete="off"
by Natanael_L on Sunday October 13, 2019 @09:32AM
(#21240252)
SHOULD does not equal MAY