----- Original Message ----- From: "David Håsäther" <[EMAIL PROTECTED]> To: "Andrew Fedoniouk" <[EMAIL PROTECTED]> Cc: "WHAT Working Group Mailing List" <[EMAIL PROTECTED]> Sent: Thursday, November 30, 2006 4:19 PM Subject: Re: [whatwg] HTML syntax: shortcuts for 'id' and 'class' attributes
| (Accidently only sent the first mail to Andrew). | | On 12/1/06, Andrew Fedoniouk <[EMAIL PROTECTED]> wrote: | > While we are on the subject of discussing HTML syntax.... | > | > How about following (wild) idea? | > | > To allow following notation (borrowed from CSS selectors): | > | > <p.myclass>...</p> is equivalent of | > <p class="myclass">...</p> | > | > <p#myid>...</p> is equivalent of | > <p id="myid">...</p> | > | > <p.myclass1.myclass2>...</p> is equivalent of | > <p class="myclass1 myclass2">...</p> | > | > <p#myid.myclass1.myclass2>...</p> is equivalent of | > <p id="myid" class="myclass1 myclass2">...</p> | > | > It is syntax sugar of course but at least it will reduce amount of data | > needs to be sent over the wire. | | 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? Andrew Fedoniouk. http://terrainfromatica.com | | -- | David Håsäther |
