Re: [whatwg] Updated index of all HTML elements

ine, that includes it: http://rawgit.com/w3c/elements-of-html/master/index.html/. (Apologies to those who’re subscribed to both WHATWG and W3C lists and who may see this message twice; the lists are separate on purpose, and yet this is related to both.) -- Jens O. Meiert http://meiert.com/en/

[whatwg] Updated index of all HTML elements

/+JensOMeiert/posts/2w14E3V7bFc.) PS. Steve Faulkner has created http://rawgithub.com/w3c/elements-of-html/master/index.html on the basis of the other index. We’ll see what we come up with overall. -- Jens O. Meiert http://meiert.com/en/

[whatwg] HTML and spec fragmentation (WHATWG)

W3C side separately, honoring the different groups’ preferences.) -- Jens O. Meiert http://meiert.com/en/ ✍ New book! http://meiert.com/everyday-adventurer

Re: [whatwg] HTML differences from HTML4 document updated

hich could have an effect on how many people actually read the document. It is a particular nuisance for print; it is also one on mobile. With neither being high per se, I suggest the cost of problem is higher than the cost of solution, and I thus hope this is worth addressing. I don’t have any

Re: [whatwg] HTML differences from HTML4 document updated

em? Yes. It’s probably a lesser important part of the document but it appears to take up about half of the space (or blows the document up to double its size, respectively). -- Jens O. Meiert http://meiert.com/en/

Re: [whatwg] HTML differences from HTML4 document updated

ent. This keeps the document length at bay while it’s still possible for people who are actually interested in all changes to go back and check for them. Cheers, Jens. -- Jens O. Meiert http://meiert.com/en/

Re: [whatwg] A plea to Hixie to adopt

essentially means always seemed reasonable to me. There are plenty of options for authors to add styling hooks if they need any, including . -- Jens O. Meiert http://meiert.com/en/

Re: [whatwg] 1.1.1 How do the WHATWG and W3C specifications differ?

> Please clarify -- (a) the decisions do not make sense or (b) not applying > them doesn't make sense? My main concern are the number of differences between the WHATWG and the W3C version, hence the question whether we’re on it at all to improve this. -- Jens O. Meiert http://meiert.com/en/

Re: [whatwg] 1.1.1 How do the WHATWG and W3C specifications differ?

make a lot of sense. This particularly refers to most of the “working group decisions.” [1] http://www.whatwg.org/specs/web-apps/current-work/multipage/introduction.html#introduction -- Jens O. Meiert http://meiert.com/en/

Re: [whatwg] abbr inside of option

y should “HTML” be acceptable but “HTML” not be permitted—in both cases, “HTML” is an abbreviation. (No need to explain the situation around the “title” element again, I just like the example.) -- Jens O. Meiert http://meiert.com/en/

Re: [whatwg] [html5] @formaction, @formenctype, @formmethod, @formnovalidate, @formtarget

w many more) are we talking about, and in how many instances would problems have arisen (I understand reuse of the same attribute values not to cause any, as in “”)? Thanks! Jens. -- Jens O. Meiert http://meiert.com/en/

[whatwg] [html5] @formaction, @formenctype, @formmethod, @formnovalidate, @formtarget

@target to serve the exact same purpose? Would any existing behavior of user agents stand in the way of this, or is there any other kind of incompatibility (examples appreciated)? Pending any oversight, allowing the same attribute names seems straight-forward, simple, and way easier to use. -- Jens O

Re: [whatwg] Suggestion for CSS-RESET property in CSS3 ((tag: css3, html5, css-reset, idea))

(to remove what you don’t need) but CSS also offers some leeway via “inherit” [2]. [1] http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#attr-style-scoped [2] http://www.w3.org/TR/CSS21/cascade.html#value-def-inherit -- Jens O. Meiert http://meiert.com/en/