Join Justin Putney for an in-depth discussion in this video Who are you going to support?, part of Problem Solving for Web Professionals.
- One of the important things to do is to decide beforehand which browsers and which devices you're going to support. You want to make sure that you get approval from your clients so there are no surprises down the road. If a bug comes up and it's in an unsupported browser or device, you can just say so. Be ready to test the browsers and target devices that you've chosen. Remember the importance of a small feedback boot. You need to be able to repeat the problem on your own system ideally. That way, you can test really quickly and develop new hypothesis.
So, you want to think about how many different browsers and devices that you can actually test yourself. It's probably only going to be a handful. One thing to think about is how similar are the browsers in your list? For instance, if both browsers were originally based on WebKit, like Safari and Chrome, then the differences are probably going to be somewhat minor, at least for the time being until the browsers diverge more. On the other hand, if you're choosing, say Chrome, and Internet Explorer 9, the differences are going to be quite big and you'll have to do a lot more testing.
So, once you've decided which browsers and devices you're going to support, you can start looking at those individual differences between browsers. In the next video, we'll look at a set of issues that specifically affect Chrome and Internet Explorer.
Learn to turn your web browser into a code inspector, cope with browser incompatibilities, perform cross-platform testing, and more. Justin Putney gives you the skills you need to address the unique problems in each new project—and ensure the quality of your design and your code.
- Using web inspection tools
- Finding and destroying HTML errors
- Locating missing assets
- Supporting Internet Explorer
- Becoming a Google search master
- Testing with online snippet editors, emulators, and more
- Testing responsive layouts
- Debugging code
- Adding new functionality