I'm hoping for a scene graph standard for HTML6 and a spec that allows multiple documents per window (which themselves could be nodes on a scene graph) instead of the one document per window.
Iframes sort-of do this already.
W3C declares HTML5 standard complete
21–30 of 82 posts
Re: W3C declares HTML5 standard complete
#22The other huge accomplishment of HTML5 is completely standardizing many fundamental parts of the web that previously were a mess of browser incompatibilities. 6 years ago, if you wanted to parse HTML, you might reach for BeautifulSoup, or libxml, or Hpricot, or Nokogiri...and they would all be subtly different in the parse tree they produced. And they couldn't do any better, because if you viewed the page in IE, or F…
> Now, IE9+, Firefox, Chrome, and Safari are all basically guaranteed to look at the same page in the same way, and the "toolsmith" parsers like Gumbo or html5lib are all rapidly converging on the standard. So it's finally possible to see a page the way a browser sees it.
The web projects I have to take part on, are a distant reality from that description.
Re: W3C declares HTML5 standard complete
#23The term "WHATWG" seems to be conspicuously absent from this article. I wonder where they factor into this announcement.
I think they already moved to living standard.
The living standard was never abandoned in the first place, and W3C's HTML5 is basically a fork of the WHATWG living standard.
Re: W3C declares HTML5 standard complete
#24Does anyone know how is Doctype versioning going to work with W3Cs snapshoting of the living standard? Or are browsers just going to ignore W3C and stick to implementing WHATWGs spec?
No browser ever paid any attention to the version of the HTML specified. The only use for DOCTYPE—and the reason it remains in HTML5—is "doctype switching", i.e. different rendering modes are triggered in the browsers. You can use "html", "html5", "html6.2" or "foobarbaz" as your doctype, the effect will be the same—they will all trigger standards compliant mode.
Re: W3C declares HTML5 standard complete
#25The most important thing about HTML5 is ? What a weird statement.
Making Flash obsolete is pretty important
Re: W3C declares HTML5 standard complete
#26Cool, but It doesn't really matter what W3C says. In the end it is all about what the Oligarchy of popular browser implementers decide to implement.
> the Oligarchy of popular browser implementers
In the past, only Mozilla cared about what the W3C said, and they built Firefox on the idea that interoperability by following the standards is the way to go. Not that long after Apple initiated Safari, and led Google to their own browser initiative.
All this because Mozilla, the insignificant actor of the all IE time, decided to follow W3C.
You're not totally wrong telling that W3C doesn't mater that much, but browsers are what they are today because of W3C for a good part, and it still have a very important place in the browser game.
Re: W3C declares HTML5 standard complete
#27Earlier quoted context omitted.
I think they already moved to living standard.
Indeed, the W3C's work on HTML5 is irrelevant. It exists only for the purpose of giving the W3C-qua-organization the appearance of being involved in the further development of HTML.
They have different purposes. In practical terms, the "HTML5 standard" is really defined by whatever the most popular browsers implement - we saw this in vivid detail when IE6 was the most popular browser and Microsoft made a mockery of the standard. The WHATWG standard exists to track the evolving consensus, so that the major browsers don't diverge too much and we don't go back to the web c. 2005. The W3C spec is so that other interested parties, ones who need to have a finalized doc to shoot for, have something to shoot for that everybody has agreed upon.
Re: W3C declares HTML5 standard complete
#28I'm hoping for a scene graph standard for HTML6 and a spec that allows multiple documents per window (which themselves could be nodes on a scene graph) instead of the one document per window.
HTML5 is a living standard, no? There isn't going to be an "HTML6".
Re: W3C declares HTML5 standard complete
#29i guess it's finally time to upgrade that .vimrc to include syntax highlighting for the new tags... canvas, video, audio, nav, section, etc..
Re: W3C declares HTML5 standard complete
#30The other huge accomplishment of HTML5 is completely standardizing many fundamental parts of the web that previously were a mess of browser incompatibilities. 6 years ago, if you wanted to parse HTML, you might reach for BeautifulSoup, or libxml, or Hpricot, or Nokogiri...and they would all be subtly different in the parse tree they produced. And they couldn't do any better, because if you viewed the page in IE, or F…
> Now, IE9+, Firefox, Chrome, and Safari are all basically guaranteed to look at the same page in the same way, and the "toolsmith" parsers like Gumbo or html5lib are all rapidly converging on the standard. So it's finally possible to see a page the way a browser sees it. The web projects I have to take part on, are a distant reality from that description.
Is there any particular reason? Requiring support for older or legacy browsers?
I just recently wrapped up a project utilizing customized Twitter Bootstrap / CSS3 / HTML5 and I was pleasantly surprised at how smooth everything went between IE/Chrome/Safari/FF. This is the first time, in a long time, that everything just "worked."