Clarify case-insensitive parsing for enum values #1142
Comments
|
Bit of history... the original version of the spec did... then we did the IDL conversion (case-sensitive/exact match)... then we got rid of the IDL conversion... but then we forgot to revert back to normalizing the case. At the same time, we were originally being a bit too liberal with the what we accepted. We shouldn't have done case normalization for enum values, but given that's what's implemented by everyone, we might as well updated the spec to match. |
|
Filed the following Gecko bug to make "dir" parsing case-insensitive as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1921633 We could then make parsing the enum-based members case-insensitive. |
|
The Gecko patch has landed, so "dir" will soon be case-insensitive there as well. Thanks @saschanaz! I filed a PR to reflect the engines' behavior in the spec. |
…ber r=saschanaz for alignment between engines: w3c/manifest#1142 Differential Revision: https://phabricator.services.mozilla.com/D224984
…ber r=saschanaz for alignment between engines: w3c/manifest#1142 Differential Revision: https://phabricator.services.mozilla.com/D224984
and others
The parsing algorithms of the current specification don't mention case-insensitive parsing of the enum-based members (
dir,display,orientation), but all browser engines have implemented this:dirdisplayorientationThe text was updated successfully, but these errors were encountered: