W3C home > Mailing lists > Public > public-html@w3.org > December 2008

Re: Void elements in HTML (Was: ZIP-based packages and URI references into them ODF proposal)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 30 Dec 2008 15:28:46 +0100
Message-ID: <495A301E.9070009@gmx.de>
To: Ian Hickson <ian@hixie.ch>
CC: public-html@w3.org

 > ...
>> The problem can be fixed by stating once and for all the syntax for 
>> future elements.
> 
> That doesn't work. It would mean never introducing new void elements and 

... which I think is no problem at all ...

> never introducing new block-level elements. For example, in HTML5, it 
> would mean not introducing <command>, <event-source>, <section>, <nav>, 
> <aside>, <footer>, <header>, etc.

Could you please explain (or point to an explanation) why exactly it 
needs to be known beforehand whether something is block-level or not? 
It's certainly not needed for serializing a DOM, so I assume the parser 
needs to know for some reason?

> ...

BR, Julian
Received on Tuesday, 30 December 2008 14:29:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:27 GMT