Solving these types of issues can be a lot more complicated than you might think. For example, take WebRTC. Lots of places wrote their WebRTC code to Chrome's

Solving these types of issues can be a lot more complicated than you might think. For example, take WebRTC. Lots of places wrote their WebRTC code to Chrome's non-standard "Plan B" dialect. Now all the browsers are transitioning to the standardized "Unified Plan." Should Mozilla have spent developer resources on implementing Plan B as a stop-gap until the Unified Plan was rolled out by Chrome, and then subsequently thrown away all the code for the former? Some people might say so, but others might argue that doing so is a terrible waste of resources. My point here is that the solution is not always cut and dried.