If any weirdness shows up in Chrome, you'll just end up comparing it to IE6.
If any weirdness shows up in Chrome, you'll just end up comparing it to IE6.
Last I checked Safari unlike Firefox and Chrome is not cross platform.
Small aside: Webkit browsers used to have problems with CSS (especially things involving 3d) when hardware acceleration is unavailable. Spent so many hours back in the day debugging why certain CSS effects did not work. Switched to Firefox and worked like a charm... Only really understood the problem when I eventually switched to a system with HW acceleration support.
'Cause if it isn't then it's not really a good proxy for testing Safari behavior in this context...
How do you that if you don't own a mac?
Whereas you’re literally saying you’re happy to walk away from over 35% of mobile users, while telling them to do something they can’t do without replacing their device. That’s… one way to run a business.
The amount of business we would be losing by ignoring mobile safari users is staggering. For whatever reason it's also the majority browser, I dont think its safe to assume that the users of your site using safari are equal to the percentage of the market share even.
Ignoring it is a very unusual stance unless your site/app is basically exclusively desktop.
Not in 2006 no. MS started providing free VMs for browser testing circa 2013, after the release of IE10.
Say what you will about IE, at least Microsoft make an attempt to make it available to everyone (via free Windows VM preloaded with specific IE version).
1. Tell customers it will cost x more money to fix bugs on Safari (likely zero will pay this premium)
2. Put a notice or banner for Safari users that they are using a non standards compliant browser and they may see minor or major issues and maybe should use Firefox or Chrome.
3. Educate customers on standards and show them alternatives so they can do the same for their customers.
4. Record actual brower useage data and demonstrate the low count of actual Safari visitors and star back at #1 above with this newly applied info.