In order to prevent such abuse from spreading, perhaps HTML5 should reparent such misplaced elements.
HTML5 is being <s>ab</s>used already, and with the earliest examples comes a reality check. This could be funny.
Too many folk in the working group believe in a prescriptive standard, to fit their point of view. This is a problem. But then I have completely failed to make that point before - so nevermind.
If i read the HTML 5 draft, i am missing easy explanations what elements are alowed in an other element. There is no coercive logic why a header may not contain a navigation. Apples website is an example for a website whichs navigation is the header.
The current spec is to nerdy written to be understandable by most authors. If the WAHTWG does really care about HTML 5 either the spec needs to be changed (i believe its possible, but don’t now if its a good idea regarding overhead) or they need to create 2 documents, one for authors, one for implementers.
The current spec is to nerdy written to be understandable by most authors. If the WAHTWG does really care about HTML 5 either the spec needs to be changed (i believe its possible, but don’t now if its a good idea regarding overhead) or they need to...