71–80 of 97 posts
Same thing but guaranteed to be up to date and (more) complete.
For example, htmlreference.io's page for doesn't mention the autocomplete attribute. MDN lists all its possible values.
http://htmlreference.io/element/input/
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/in...
Guaranteed to be up to date and (more) complete.
For example, htmlreference.io's page for doesn't mention the autocomplete attribute. MDN lists all its possible values.
I believe your kbd example is incorrect. You suggest > To save, press Ctrl + S . But the spec (both W3C and WHATWG) suggests that individual keys should be nested inside an outer tag: "When the kbd element is nested inside another kbd element, it represents an actual key or other single unit of input as appropriate for the input mechanism." Thus, the example should be: > To save, press Ctrl + S . Cite: https://w3c.gi…
Update: Looks like the tag dates to the first draft of HTML 2.0 in 1993, where it was defined as "in an instruction manual, Text typed by a user." ( https://tools.ietf.org/html/draft-ietf-iiir-html-00 ) It remained more or less the same through HTML 4.01: "Indicates text to be entered by the user." The notion of using nested kbd tags to indicate literal keys appears to have been introduced by WHATWG when working on H…
Did that follow common usage at the time?
Earlier quoted context omitted.
It's the voluntary nature of the payment and whether the cost is tangible to you that determine what is free, not the currency used. Substitute "your FBI file" for your ad network profile and "compute time on your Amazon instance" for JavaScript time in your browser to make this clearer.
Tell me more about this Silicon Valley place where everything is magically free?
Good stuff. Would be even nicer if it showed information about optionally self-closing tags, which is one of the main reasons I occasionally need to look at the spec. For instance: > A p element's end tag may be omitted if the p element is immediately followed by an address, article, aside, blockquote, div, dl, fieldset, footer, form, h1, h2, h3, h4, h5, h6, header, hgroup, hr, main, nav, ol, p, pre, section, table,…
Edit: to expand a bit, the link is to a pretty readable/hyperlinked DTD grammar for HTML (W3C HTML 5.1)
Good stuff. Would be even nicer if it showed information about optionally self-closing tags, which is one of the main reasons I occasionally need to look at the spec. For instance: > A p element's end tag may be omitted if the p element is immediately followed by an address, article, aside, blockquote, div, dl, fieldset, footer, form, h1, h2, h3, h4, h5, h6, header, hgroup, hr, main, nav, ol, p, pre, section, table,…
Earlier quoted context omitted.
Update: Looks like the tag dates to the first draft of HTML 2.0 in 1993, where it was defined as "in an instruction manual, Text typed by a user." ( https://tools.ietf.org/html/draft-ietf-iiir-html-00 ) It remained more or less the same through HTML 4.01: "Indicates text to be entered by the user." The notion of using nested kbd tags to indicate literal keys appears to have been introduced by WHATWG when working on H…
> The notion of using nested kbd tags to indicate literal keys appears to have been introduced by WHATWG when working on HTML5. Did that follow common usage at the time?