> If what browser developers prefer to use has a significant influence on testing of anything other than experimental prototype / proof-of-concept work, the pro

> If what browser developers prefer to use has a significant influence on testing of anything other than experimental prototype / proof-of-concept work, the problem that needs to be addressed is testing practices, not developer browser choices. I don't disagree that testing practice as far as cross browser testing isn't quite where it should be. However changing testing practices is a harder problem than creating diversification in developer teams. When I switched from Chrome to Firefox in my team I shifted the balance from 10 people using Chrome to 9 people using Chrome and 1 using Firefox. Running Firefox often surfaces problems in both our product and in those of other people. > Trying to fix it with the latter won't work, it will just make different projects having different improper testing biases, which will make the web broken in all browsers instead of just non-Chrome browsers. Striving for a diverse set of browsers used in any developer team helps, but tackling the testing biases is important. At a larger scale reducing the share of Chrome users on the web is a good in itself.