HTML5 – What I don’t like?

I have not read everything about the HTML5, but whatever I have read and come to know from different places, I have these objections in HTML5 specification, which is still in draft mode.

  • HTML5 has no restriction on attributes value quoted or not.
  • HTML element name can be small case or capital.
  • It can be closed or not (<img /> or <img>).
  • There is no order or number of times fixed for elements like <header>, <footer> etc. and footer element can come on top and I saw it is still valid markup.
  • XHTML has been started for the reason that browser resource has been wasted in correcting markup. Why do they not make this fixed for quoting attributes value and closing each element? Even if someone do not close their markup, page renders in browser. So, why to include this kind of mistakes in HTML5 spec.
  • # 1 - by Ryan

    So you are unhappy that the HTML5 spec defines how to handle all HTML, including pre-existing content and author’s syntax errors? Really? Does this make sense to you? WHATWG encourages you to adopt best practices and therefore allows you to follow syntax rules previously defined for XHTML. The problem is both user agents and authors, not a spec sheet that you clearly didn’t read.

    Maybe you should change the title to “What I don’t like or know about HTML” because you obviously have never used HTML (regardless of version).

  • # 2 - by Ryan

    So you are unhappy that the HTML5 spec defines how to handle all HTML, including pre-existing content and author’s syntax errors? Really? Does this make sense to you? WHATWG encourages you to adopt best practices and therefore allows you to follow syntax rules previously defined for XHTML. The problem is both user agents and authors, not a spec sheet that you clearly didn’t read.

    Maybe you should change the title to “What I don’t like or know about HTML” because you obviously have never used HTML (regardless of version).

  • # 3 - by Satya Prakash

    Encouraging is something different. Including something in spec itself is something different.
    Why to include something not useful in spec!
    Browser developer will always try to render html as much correctly as they can. so mentioning about wrong doing in spec. does not make sense.

  • # 4 - by Satya Prakash

    Encouraging is something different. Including something in spec itself is something different.
    Why to include something not useful in spec!
    Browser developer will always try to render html as much correctly as they can. so mentioning about wrong doing in spec. does not make sense.

Comment pages
1 2 995
Comments are open for an year period. Please, write here on Facebook page.