They are only supported in new browsers. I think everyone here knows that. But if majority of users are still on older browsers that don't support CSS3/HTML5, shouldn't that push developers to use older scripting languages (ie:HTML4/CSS2).
+1
A:
As the article above states, there is ExplorerCanvas until IE supports the <canvas/> tag.
There is also svgweb until IE supports SVG.
And Microsoft announced CSS3 support in IE9. As IE is pushed through Windows Update, I'm not afraid of using CSS3 and HTML5 right now.
Gregory Pakosz
2009-12-12 14:42:42
IE has never given any indication of supporting canvas. I've heard of problems with svgweb on IE but don't recall what they were (slow?). While IE9 may "add" some CSS3 support, it doesn't mean it will approach all the other browsers.
Rob
2009-12-12 15:28:09
+5
A:
They are both draft specifications which are partially supported (to various degrees) in current browsers.
shouldn't that push developers to use older scripting languages (ie:HTML4/CSS2).
Leaving aside neither of those being scripting languages…
Using draft features can provide a better experience in some browsers, while the fallback is still acceptable.
JavaScript can sometimes be used to support browsers which don't have native support for a feature (although usually with a performance hit for those browsers).
Building around draft features provides practical experience with how those features work (and helps determine if there needs to be more work on the design before the feature goes into a final specification).
Building JS based around draft features gives common ground for different developers to aim for when building scripts to achieve a specific task. This increases the interoperability and ability to switch third party scripts.
David Dorward
2009-12-12 14:45:18
A:
shouldn't that push developers to use older scripting languages (ie:HTML4/CSS2)?
If that's your only question, then your answer is yes. "Most" developers are still using HTML 4.01 and mostly CSS2 for the reasons you stated: they're well supported on today's popular browsers. :D
See these:
support of CSS3 among common browsers (not very good yet..)
CrazyJugglerDrummer
2009-12-12 14:45:21
+3
A:
No, we as developers need to push forward. Tools like Google Chrome Frame and Explorer Canvas will allow us to push the edge without too much worry about the browsers that can't keep up.
Ryan McGeary
2009-12-12 14:46:52
With regard to Frame: you're still dependent on whether the client installs that or not. Besides, I find it nonsensicial. Why would you improve an ancient browser instead of just installing a brand new browser? Then rather do something like as http://ie6nomore.com.
BalusC
2009-12-12 15:24:17
BalusC, Because, ironically, some organizations allow employees to install IE plugins as opposed to switch to another browser. In principal, I agree with you though.
Ryan McGeary
2009-12-12 17:35:06
A:
I'd say, use the broadly supported options now but make sure that your designs degrade 'gracefully' with browsers that don't support these new features as they will just ignore them.
Lazarus
2009-12-12 15:13:14
A:
HTML5 is mostly backwards compatible with HTML4.01, and the same browsers will still be able to handle HTML4.01 elements. Like all properties in CSS, developers will be aware and careful of how the CSS3 properties they use will affect users who can't see them (typically IE users).
Rob
2009-12-12 15:30:07
+1
A:
As @Rob states most of HTML5 is just HTML4 with defined error handling. Assuming you are not using the new parts of HTML5, there are no disadvantages and several benefits to using the HTML5 doctype now, including a better spec and a better validator.
A lot of CSS3 (rounded corners, drop shadows, RGBa, @font-face…) can be used as progressive enhancement on top of CSS2.1 rules. Conveniently this is also the CSS3 that is most implemented.
I think this question points to either a misunderstanding of HTML5 & CSS3, or a misunderstanding of underpinning concepts like progressive enhancement, the web trifle/layer cake, and the cascade.
For further explanation, please refer to: Do websites need to look exactly the same in every browser
Boblet
2009-12-13 13:44:06