13851 2011-08-21 04:19:50 +0000 Title:Semantics, structure, and APIs of HTML documents. About the new Html 5 tags i have some confusion. If the new tags just has semantic meaning than what is the point of including too many tags in the new html version. Its like the browser wars all ove 2011-12-03 03:35:29 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#top P3 normal --- 1 contributor contributor ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 55542 0 contributor 2011-08-21 04:19:50 +0000 Specification: http://www.w3.org/TR/html5/ Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: Title:Semantics, structure, and APIs of HTML documents. About the new Html 5 tags i have some confusion. If the new tags just has semantic meaning than what is the point of including too many tags in the new html version. Its like the browser wars all over again as every browser will want to add their own tags and features in the already cluttered html markup. We all love old school "DIV" .It was simple and easy to learn. A new tag added to html 5 is a new tag that has to be learned by everybody. And as you know that learning new thing is a thing that the developer community is not very good at. Some may hate the changes. So As a you are a w3 representative i wanna give a suggestion about semantics of the tags. I think we should be using old divs as usual. And there should be something like reserved "ID"s and instead of <header>, <div id="HEADER"> should be parsed or understood by browser as header in the page. This way the user and the old browser will be immune to the fast changing web specification. You were saying that google can understand the ids given to divs so why browser can't??? To differentiate between reserved ids from regular ids we can do something like CAPITALIZE them or append a special character at beginning like id="$header" id="$footer". If we are just using <header> and <footer> tags that doesn't means the developer will not be giving them ids. So why don't just giv id to old school divs .That way backward compatibility will be also ensured... And browser maker can also be relaxed as they don't have to release a new version every time a new tag is discovered. Posted from: 202.159.215.190 User agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20100101 Firefox/5.0 60880 1 ian 2011-12-03 03:35:29 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: <div id="header"> seems longer than <header>. I don't see much point doing that. The compatibility argument isn't strong since everyone now basically supports <header>.