[w3c/manifest] Clarify case-insensitive parsing for enum values (Issue #1142)

The parsing algorithms of the current specification don't mention case-insensitive parsing of the enum-based members (`dir`, `display`, `orientation`), but some browser engines seem to have implemented this:

| User Agent | [`dir`](https://www.w3.org/TR/appmanifest/#dfn-process-the-dir-member) | [`display`](https://www.w3.org/TR/appmanifest/#dfn-process-the-display-member) | [`orientation`](https://www.w3.org/TR/appmanifest/#dfn-process-the-orientation-member) |
| --- | --- | --- | --- |
| Chromium | _not implemented yet_ | 🤷🏼‍♂️ [case-insensitive](https://github.com/chromium/chromium/blob/main/third_party/blink/common/manifest/manifest_util.cc#L69) | 🤷🏼‍♂️ [case-insensitive](https://github.com/chromium/chromium/blob/main/third_party/blink/common/manifest/manifest_util.cc#L127) |
| Gecko | 🚨 [case-sensitive](https://github.com/mozilla/gecko-dev/blob/master/dom/manifest/ManifestProcessor.sys.mjs#L134) | 🤷🏼‍♂️ [case-insensitive](https://github.com/mozilla/gecko-dev/blob/master/dom/manifest/ManifestProcessor.sys.mjs#L193) | 🤷🏼‍♂️ [case-insensitive](https://github.com/mozilla/gecko-dev/blob/master/dom/manifest/ManifestProcessor.sys.mjs#L174) |
| WebKit | _not implemented yet_ | 🤷🏼‍♂️ [case-insensitive](https://github.com/WebKit/WebKit/blob/main/Source/WebCore/Modules/applicationmanifest/ApplicationManifestParser.cpp#L188) | 🤷🏼‍♂️ [case-insensitive](https://github.com/WebKit/WebKit/blob/main/Source/WebCore/Modules/applicationmanifest/ApplicationManifestParser.cpp#L215) |

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/1142
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/1142@github.com>