This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Let's rename no-quirks mode to standards mode and limited quirks mode to almost standards mode. Even though quirks are specified, the names "standards mode" and "almost standards mode" seem to continue to be used everywhere except in spec prose. Let's align with de facto terminology and not confuse people unnecessarily.
Hixie, strong opinion?
It makes no sense to have a mode called "standards mode" when every mode is standardised. I do not plan to make any changes along these lines in the HTML spec.
Similarly it makes no sense to have a mode called "quirks mode" or "no-quirks mode" when every mode has quirks. So if you have that line of argument, you need a different set of names altogether. I stand by the argument that we serve our readers better by using the names they already know, and then leave our sense of logic at the door.
I'm happy to consider names more accurate than "no-quirks" and "limited-quirks". "Standards mode" implies that the other modes don't follow the specs, which I think is a significantly worse problem than using new terminology.
Why is it a problem?(In reply to comment #4) > I'm happy to consider names more accurate than "no-quirks" and > "limited-quirks". That's missing the point. We should use the names people already know and use and will continue to use regardless of what the spec says. Using different terminology is a problem because it forces all readers to mentally translate your terms to quirks mode, almost standards mode and standards mode. > "Standards mode" implies that the other modes don't follow > the specs, which I think is a significantly worse problem than using new > terminology. I don't see why it is a problem at all.
For other terms we usually side on what our readers know. Examples from the Terminology section: "URL" (instead of URI or IRI) "MIME type" (instead of Internet media type) "plugin" (instead of content handler as the spec had before) "JavaScript" (instead of ECMAScript)
Resolving as wontfix because the status quo is okay, renaming is a pain, and the old names are vetoed by Hixie.
http://hsivonen.iki.fi/almost-precedent/ Reminds of why I consider "HTML5" a misnomer even as a buzzword.