- From: Michael[tm] Smith via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 Mar 2020 14:25:55 +0000
- To: public-device-apis-log@w3.org
> If the attribute value matches none of the given keywords, the invalid value default maps to an implementation-specific state that indicates to the implementation to act according to its default behavior. That applies to the action of the implementation, which is orthogonal to the document-conformance requirements (authoring-conformance requirements). The issue is that the document-conformance requirements explicitly state that `user` and `environment` are valid keywords, but don’t explicitly state that the empty string is a valid keyword. For the empty string to be considered a valid value that documents and authors are allowed to use, it must be explicitly included in the same spec sentence that begins with *The attribute's keywords are `user` and `environment`*. Compare to https://html.spec.whatwg.org/multipage/interaction.html#contenteditable: > The `contenteditable` content attribute is an enumerated attribute whose keywords are the empty string, `true`, and `false`. Or compare to https://html.spec.whatwg.org/multipage/media.html#attr-media-preload, which states that for the`preload` attribute, *The following table lists the keywords and states for the attribute*, and then lists `none`, `metadata`, and `auto`, followed by this statement: > The empty string is also a valid keyword, and maps to the Automatic state. -- GitHub Notification of comment by sideshowbarker Please view or discuss this issue at https://github.com/w3c/html-media-capture/issues/34#issuecomment-602628812 using your GitHub account
Received on Monday, 23 March 2020 14:25:57 UTC