4 ms·

Definitely, it's very fine to use HTML5/CSS3. However, I think that it is still a good idea to make it fall back nicely. Stuff like rounded corners aren't too t

Definitely, it's very fine to use HTML5/CSS3. However, I think that it is still a good idea to make it fall back nicely. Stuff like rounded corners aren't too tragic to lose when viewing something from IE6-8, but I think it's in your best interest to make sure that IE7 and 8 don't look dreadful. Reward people for using better browsers, but don't punish them for using bad ones either. Completely ignore IE6, don't even worry about how it looks. Most startups nowadays buy a computer and at least IE7 is on it. 2011 should be a big year for HTML5, so aim towards the "future". Don't worry about IE<9 too much, but certainly make sure it falls back gracefully is what I'm saying. It's okay if it's not as pretty, as long as the basics work.

prateekdayal 16y ago
Thanks for the reply. I was planning on using some of the features like localStorage and notifications etc and not just css3 features for making things look better. Nevertheless, I think its a good idea to have graceful degradation.
- ashamedlion 16y ago
  Ah yes, those are good ones to use. I say screw it and use stuff like that. Just make sure that on your marketing page you explicitly say which browsers are supported so that you don't get a bunch of angry customers :)
- Isofarro 16y ago
  Use wrapper methods/classes for each of those HTML5 specific features. Initially, probably for most of the early adopter phase you can get away with using/expecting the HTML5 feature to be present. When you do need to support browsers that don't support or brokenly support those features, you can add in support at the wrapper level without having to do any serious refactoring. Also, keep a careful eye on the HTML5 draft recommendations, just in case features change their implementations. It's unlikely for a feature supported in two independent modern browsers to change unless there's a fundamental problem, or patent workaround needed.

prateekdayal 16y ago

Thanks for the reply. I was planning on using some of the features like localStorage and notifications etc and not just css3 features for making things look better. Nevertheless, I think its a good idea to have graceful degradation.

ashamedlion 16y ago
Ah yes, those are good ones to use. I say screw it and use stuff like that. Just make sure that on your marketing page you explicitly say which browsers are supported so that you don't get a bunch of angry customers :)
Isofarro 16y ago
Use wrapper methods/classes for each of those HTML5 specific features. Initially, probably for most of the early adopter phase you can get away with using/expecting the HTML5 feature to be present. When you do need to support browsers that don't support or brokenly support those features, you can add in support at the wrapper level without having to do any serious refactoring. Also, keep a careful eye on the HTML5 draft recommendations, just in case features change their implementations. It's unlikely for a feature supported in two independent modern browsers to change unless there's a fundamental problem, or patent workaround needed.