Andrew Fedoniouk wrote:
| >
| > <p.myclass>...</p> is equivalent of
| > <p class="myclass">...</p>
| >
|
| HTML5 is meant to be backwards compatible, so this is out of the question.
And where do you see problems with backward compatibility?
Or let's put this way: what would be a definition of backward compatibility in
terms of HTML5?
Anything specified in HTML5 must degrade gracefully in pre-HTML5
software. Unless at the very least current browsers parse <p.myclass> as
<p> this proposal is unworkable under this constraint.
