Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When a new specification comes out (like HTML 5) it can be tempting to begin using its enhancements; however, how do you deal with the fact that not all browsers will be up to snuff with the latest and greatest specs? Surely, it’s no fun having to code the same thing twice. While we can take advantage of things that degrade gracefully, isn’t it just easier to use what’s available to all of today’s common browsers? What’s your practice (or waiting period) for adopting new specs?
In the case of HTML5, I will probably no adopt it for any “core” functionnaly of a website before the required functionnalities are supported by the webbrowers used by something like 90% of my users — which means, unfortunatly, not that soon for any “general” site 🙁
Maybe when something like 80% of my users support the most imteresting parts, I’ll start using those, and degrade gracefully for the others, though…
But you’re not always the one deciding : your clients are often the ones who choose… And if they’re stuck with IE6 because of company-policy and the like… and yes, there are too many users stuck on IE6, without the ability to upgrade / use anything else.
For instance, take the new
<video>tag : how will you convince your clients that you should use it in their website, when they already have some embeded flash stuff that works just fine for more users than the ones who would be able to read the<video>tag ?