-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The empty string is not defined as a conforming value for the capture attribute #34
Comments
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. IIRC this design was for historical reasons. |
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 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 Compare to https://html.spec.whatwg.org/multipage/interaction.html#contenteditable:
Or compare to https://html.spec.whatwg.org/multipage/media.html#attr-media-preload, which states that for the
|
@sideshowbarker thanks for the clarification, PTAL #35 |
At https://w3c.github.io/html-media-capture/#the-capture-attribute the spec states:
…but the spec does not define the empty string as a conforming keyword.
Because the spec doesn’t define the empty string as a conforming keyword, the following example from the spec itself doesn’t conform to the actual requirements in the spec —
The text was updated successfully, but these errors were encountered: