Tag Info

Hot answers tagged

2

Doctype and Microdata shouldn't create many problems. It's possible that it will throw IE into 'quirks' mode, but you will probably be fine. The problem with HTML5 tags like header and article are that older browsers don't recognize them as block level elements. So if you are using them in that way at all you may be in for some layout surprises. There are ...


2

You are correct, some older browsers like Internet Explorer 8 provide little to no support for HTML5 elements and other HTML5 features. There are online sites which can help you identify what's missing in IE 8 and older browsers, such as this one. There are also open-source projects like this often-cited one, aimed at improving HTML5 compatibility for IE 8: ...


1

This is entirely relative aka, it all depends. I've never had a case where I decided to give up on an IE version. Are you building with web standards? and testing? what's the major issue(s)? A few thoughts: No it is never acceptable to shut down browsers and shut out users. Never do that. Ok so you have to do it. Your plan to ice out < IE9 via cc ...


1

The two approaches are: Install all the browsers that you can on the computers that you have. You'll need multiple platforms: Windows, Mac, Android, iPhone, etc. Emulators and virtual machines can help. Microsoft released virtual machines for testing various versions of Internet Explorer. I can even get these to work on Linux. There are many phone ...


1

I don't think you want to state browser support in "legal" terms. Most sites add something like: Tested using the following browsers: Browser icons (with version numbers) Alternatively, you could include screenshots with different browsers to demonstrate this, or provide a link to results from an online screenshot service like this one: Browser Shots ...


1

I like to use Normalize.css whenever I possibly can on a new project. It's better than Eric Meyer's CSS Reset in that it actually provides "standardized" styles for elements, as opposed to removing all styles. So yes, it's a great starting point for a new project. You'll want to ensure that the framework or CMS your using won't conflict with it, but it's a ...


1

It's just a tool. You need to evaluate whether or not it's appropriate to use for yourself. For any given project, you might be using some other elements that conflict with it, for all we know. It's a handy library, but nobody can really make a blanket statement that you should/not use it for every project you do.



Only top voted, non community-wiki answers of a minimum length are eligible