W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2011

[whatwg] Giving the <body> tag a new meaning.

From: Liam Hockley <liamhockley@hotmail.com>
Date: Tue, 1 Mar 2011 19:05:21 -0600
Message-ID: <SNT121-DS1306B4EA229A80DF1432E4B9C00@phx.gbl>
It just seems to me that there are so many tags being added, why keep adding and adding? Down the line, it's gonna create nothing but abiguity in documents and mass confusion (especially in terms of rendering) as a result. I think that adding a <content> tag as children for <header> and <footer> or any other tag for that matter, is downright redundant and unneccesary. Them tags themselves are a "<content>" tag of sorts, they just have semanticly meaningful names. Lets face it, <content> may as well be a <div> as far as semantics go. The best solution would be to use what we have and just not require the use of the <body> tag at all. Have it remain as a legacy tag, but for the love of god, why would you add a new tag with almost the same purpose as the tag you propose nesting it in?
That's my 2c.
-Liam
>
> I neither write nor speak English natively, but I believe that the
> body element has to
> be preserved all but as it is, if only for compatibility. Instead, you
> should propose
> putting the main content inside another element inside the body element,
> say
> <content>.
>
I agree, <body> must remain for compatibility, perhaps also able a new tag
for its task, and deprecate its current meaning in future versions.
<content> may be a good option as a <header> and <footer> sibling. And say
"not required, but if implemented, do it the right way".
Received on Tuesday, 1 March 2011 17:05:21 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:31 UTC