What browsers should be installed by the layout designer to check the layout according to current realities?

Question

HTML

Hello. When I was just studying the material, one "working" firefox was enough to see the results. But, you need to move to a new level. Tell me, what browsers, according to current realities, should be installed by a person who is seriously engaged in layout? I'm not talking about layout for the enterprise, where, probably, verification is carried out for all browsers with a share of more than half a percent, but, let's say, the level of requirements that are usually made for layout layouts, which are performed by a freelancer with good recommendations.
I have a working computer on Ubuntu, with a virtual machine (Virtual Box) where there is a seven. What browsers do you recommend?

Answer 1

Usually this is chrome from version 20. Opera 10+ (although if for yourself, then 12+), Firefox (may be different), but you can try 17+, for example, if you choose. Safari 5.1+. IE depending on the segment. If to itself, then IE9+. If you want to reach as wide an audience as possible, then IE8+, because. it still has a significant market share. In addition, I would advise you to install a virtual machine with MacOSX. In it, install Xcode and the iOS device simulator. In order to check the work on iphone and ipad on ios6-7. Or pay browserstack and check there.

Answer 2

The standard set is Chrome, FireFox, Opera, Safari, IE, but I also like to play with online-checker's, like:
https://browserling.com/
https://browsershots.org/
And of course, don't forget about the mobile zoo devices

Answer 3

Browser support requirements should be agreed with the customer. But usually it's Firefox, Chrome, Safari (there are a lot of troubles with it), for the Russian-speaking segment it's worth running into Opera, but in fact in the latest versions there are much fewer problems with it (due to the transition to blink). And of course IE9+ (if there is no agreement not to support the ninth one).
In general, there is no difference in the scale of projects. Things like prefixes and so on are better left to things like autoprefixer, for a bunch of things there are polyfills and shims (for example, you can safely use es5 in ie by simply including a polyfill, or add support for selectors in ie, ala :valid, for ie less than version 10 That is ,
in fact, it all comes down to modernizer, polyfills, autoprefixer, and smoke tests of layout in all supported browsers.

Answer 4

For some reason, no one remembered the mobile web. That's where the circus is! Not even with browsers, but with screen resolution... But there is also a zoo of browsers, and, by the way, for different platforms. If I wasn't "for the enterprise [...] Usually it's IE7+" I'd be crying tears of blood I think :)

Answer 5

The main browsers are IE, Firefox, Chome, Opera, but users are different, so you also need to take into account browser versions.

Answer 6

it is precisely such requirements as you described that are usually made by average customers, why should you ignore your audience?
test for everything that is more than half a percent

Answer 7

I'll add www.lunascape.tv to Artyom Komarov 's answer . Interactive testing is not available in the wonderful https://browsershots.org/