[Bug 13851] New: 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

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13851

           Summary: 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
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#top
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


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

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Sunday, 21 August 2011 04:19:54 UTC