CSS3 and HTML5

[cyclotron]

How much is this community in to CSS3 and HTML5? I am currently looking for a job and find that many positions are looking for more than just clean CSS that displays properly. Some are asking about CSS3 and HTML5 in the interviews. Therefore I have been reading about them on the Internet.

I have one question that I thought would be best asked here: Are we supposed to care what the page looks like without CSS and without Javascript? I have tried my best with each site that it would look decent in plain old HTML.

The reason why I ask is that some of the CSS3 and HTML5 tips I have been reading degrade well into CSS2.1, but they will not look right in older, non CSS browsers/ parsers.

Other than that, I think it would benefit this community if some of the Disscussions were limited to CSS3 and or HTML5.

[chrishirst]

Well.

It's TWELVE years before HTML5 is likely to be released and probably another four or five years after that before mainstream browsers support ALL the features.

CSS3 is a little different as it is being released in modules rather than a monolithic approach, presumably to avoid the debacle that CSS2/2.1 still is.
So browsers are in various stages of CSS3 support, hell, some of them (Ok one of them) do not support a lot of CSS2 features as yet.

So limiting discussions to CSS3 and/or HTML5 might just be a little previous.

[svendenotter]

IE9 is coming up end of september and they support it. So it's coming up. But IE6 is still a browser you should focus on while building a website so it will take years before every browser is compatible with it.

What you could do is style objects with CSS3 that way that it looks the same when you watch it in not compatible browser but then withouth the outer glow, or shadow. So people who can't see the CSS3 do not miss anything and those who can see CSS3 just have that little bit of extra style to your website.

We should just code in CSS3 and HTML5 for those who can see it. Some websites should make the difference =D

[Phreaddee]

It's TWELVE years before HTML5 is likely to be released and probably another four or five years after that before mainstream browsers support ALL the features.

dont know where this 12 year figure comes from according to w3.org "The expectation is to issue the Last Call document at the end of May 2011" I cannot see it taking 12 years to get from last call to candidate recommendation.

in any case the major browsers do all support html5, firefox, safari and chrome and with a simple script so does ie back to ie6 so personally i cannot see any logical reason as to why not use html5 now. its a much simpler and logical way of coding too.

i now do all my sites in html5 and where appropriate add css3 elements but that is generally only things that will still look ok if not rendered with css3. I test with ff(3, 3.6,4), safari, opera, chrome, ie (6,7,8) and have yet to come across any issues with html5 elements not being read by the older browsers.
just the same old ie issues.

[chrishirst]

The date of 2022 came from the W3c's HTML 5 specification editor Ian Hickson, some 18/24 months ago, and the LC Candidate timeline (http://lists.w3.org/Archives/Public/public-html/2010Sep/0074.html) is the first time the W3c have issued anything to contradict that view/opinion.

Maybe the glacial progress of the W3c has finally reached warmer waters

Because of the way that HTML5 (and CSS3) are being specc'ed (in a modular manner) we may actually see browser support progressing along at a similar pace.

IE7 is now out of support so what we have now is what will remain, but because there is now a stable and usable Windows OS with Windows 7, The demise of IE7 should not be as much of a protracted affair as the death throes of IE6 have been.

Now it should only be a matter of knowing your target audience to determine if HTML5 is the right spec to use or not.