W3C and WHATWG split on HTML5 spec
- Last post
- 5 Responses
LOL.. what a mess this is going to be. 1990s here we come.
Yeah Hickson... forking and browser vendors deciding what features they will support independently from W3C has ALWAYS led to great things.
What a joke.
"Until now the two standards bodies working on HTML5 (WHATWG and W3C ) have cooperated. An announcement by WHATWG makes it clear that this is no longer true. WHATWG is going to work on a living standard for HTML which will continue to evolve as more technologies are added. WC3 is going the traditional and much more time consuming route of creating a traditional standard which WHATWG refers to as a 'snapshot' of their living standard. Of course now being free of WC3's slower methods WHATWG can accelerate the pace of introducing new technologies to HTML5. Whatever happens, the future has just become more complicated — now you have to ask yourself 'Which HTML5?'"
Freakin' bingo! :)
I don't know WHATF is going on WWJD?
- Wwjd? Probably get his raptor moonwalk on.Hombre_Lobo
i just know WWW
Bring Back Flash™
- no plugins thanksinteliboy
- yep.. this HTML thing will work out awesomely it seems.monolith
- I miss Flash so much.CyBrainX
Hmm... this actually sounds realistic, no?
Browser Devs have been pushing the old limits of W3C versioning anyway — 'html5' isn't supposed to become a resolved spec for another few years anyway, isn't it? — so as long as they continue to support the WHATWG, falling back on W3C, then all's good and the same as now, no?
Or am I missing something? (I probably am).
- This was my initial thought, as well.duckseason