[gkbrk]

I am not sure about that. Usually, when people only use Chrome to test and develop; Firefox/Safari users end up with problems. When someone tests on Firefox; things usually end up working on Chrome without problems.

This might be due to Firefox users being more aware of standards than just "whatever runs on Chrome today", or because Google tends to ship non-standard behaviour with their browser and make it a "standard" with their massive marketshare. Or it might be related to Firefox developers implementing the standards more carefully in order to protect their shrinking marketshare.

In my experience people get way more complaints when the developer uses Chrome and the user uses Firefox than the other way around.

[HenryBemis]

I remember auditing the ebanking system for a bank a decade+ ago.

I was expecting that they perform their UAT on the prevalent browsers at the time. I don't expect/demand that people will UAT a website for "Pale Moon", but it is dangerous to not test Firefox, Safari, Chrome, Opera (and a few more) and in multiple devices/displays.

I have no expectation that a personal blog will display perfectly, but for some applications/websites every menu option, line, frame, must be perfecly visible as per the design, otherwise you get your Chrome users that cannot hit "send" to complete that funds transfer, and that won't keep you employed for long.

[jacob019]

This. I develop against firefox only, internal apps for my company. It's been many years since something was funtionally crippled in Chrome. At worst some ugly UI elements.

[sjwright]

Exactly this. I have no desire to develop against the most bleeding edge target. Thanks for explaining this better than I could.

[ArneBab]

Do you remember the IE4-Days? DHTML? That’s what Chrome might become.