However, this is policy. E.g., as an independent vendor or developer, your priorities are probably: "Let's make sure this works on all (or most) major browsers

However, this is policy. E.g., as an independent vendor or developer, your priorities are probably: "Let's make sure this works on all (or most) major browsers before release." Probably, you have a list of high priority compatibility targets and a list of lowers ones, and there's some room for taste and judgement here. But, if your list of high priority targets consists just of your own products, you're much on the former path of the Microsoft, back when they arguably had some problems with their priorities. Edit: I once had a conversation with a Chrome developer, when Chrome 32 broke the established behavior of source buffers in the Web Audio API. I was really surprised to learn that they were working in total isolation and didn't even know how other major browsers behaved and what the established behavior was. I wouldn't blame the individual developers, but I'd expect there to be a process in the corporate culture to check such things (at least) before release. (Are we breaking anything?) Having no such a process – and by this favoring your own product and vision over standards – is arguably an aspect of corporate policy. Especially, if you have all the resources to establish such a process.