3 ms·
My standard is the browser ~95% of my users use. It's the only meaningful one. I still fix FF bugs when they come in (it seems to be a bigger offender than IE
by ng12 8y ago
My standard is the browser ~95% of my users use. It's the only meaningful one.
I still fix FF bugs when they come in (it seems to be a bigger offender than IE recently) but developing for Chrome first is the only approach which makes business sense.
- robin_reala 8y ago95%? I haven’t seen less than 20% mobile Safari on any site I’ve worked on in the last few years, and that’s not even including Edge / IE / Firefox and desktop Safari.
- ng12 8y agoOur users are almost exclusively professionals working on Windows desktops. Probably a fairly unique situation but the point is standards are relative.
- kkarakk 8y agoonly true in american markets
- robin_reala 8y agoI was actually talking about UK and Sweden (haven’t been to the US in 15 years).
- kkarakk 8y agowhat's the difference? these countries are basically american markets, everything west of belarus is kinda a software monoculture
- aaaaaaaaaaab 8y agoYou would have loved IE6 back in the day.
- noir_lord 8y agoI get to mandate the browser the work system supports (which is Chrome because that was what the majority of users used when I started so I went with what would cause the least amount of pain) but every feature I rollout works with Chrome, Firefox and mobile Safari (I test all three). It adds very little extra work with the advantage of surfacing edge cases/issues that might have bitten me even if it was just Chrome in the mix. Also from a business risk point of view tying the entire platform to a capricious vendor is dangerous and I've been around long enough to remember the days of IE5 then 6. Once bitten, twice shy.