4 ms·
Now we are getting somewhere. But, why do we even need a HTML 4.2 or a CSS3? Bundling these standards up into giant documents doesn't do anybody any good. First
by briansmith 18y ago
Now we are getting somewhere. But, why do we even need a HTML 4.2 or a CSS3? Bundling these standards up into giant documents doesn't do anybody any good. First, we should try writing a separate document for each new feature, standardizing each one individually. Then, browsers will have HTML 4.01 + CSS 2.1 + <canvas> + <video> + CSS opacity + CSS 2009 Selectors + Query Selectors + Cross-Domain XHR.
- jacobolus 18y agoI imagine that if you're willing to write and maintain a spec, and build a community around it, for one of these bits (think a full time job for one or two people, at least), the HTML5 guys would be totally happy to sign the responsibility over.
- kwamenum86 18y agoSeems much more complicated than even the current setup where browser either do not implement all features or implement them inconsistently. Browser-building companies interact with the standards a bit differently than the rest of us (I am assuming you do not work on IE, Firefox, Opera, Safari, Chrome etc.) Separating features into separate documents likely does not affect their process much.