It last happened with Safari when it was the overwhelming majority of mobile traffic market share. That was even a meme for a while in the web developer community around 2010-2015 or so: "Safari is the new IE."
It took years for Android's growth to make it a credible second browser for mobile devs to care about, and to pressure Apple to catch up to web standards faster.
> ...pressure Apple to catch up to Google's web standards faster.
Ftfy.
Safari is the only brake we have in this rush towards complex and unmaintainable web, with Google (the only company which can afford to play this game) at the helm. So no, Safari not supporting some random new feature is not a bad thing.
During the "Safari is the new IE" era though, Apple had created all sorts of proprietary extensions to make websites more mobile-friendly... a whole slew of nonstandard `-webkit-*` prefixed CSS properties and DOM events.
I can't say for sure whether pressure from Google got all that stuff migrated into real web standards faster or not, but it sure felt at the time like it was having that effect.
It took years for Android's growth to make it a credible second browser for mobile devs to care about, and to pressure Apple to catch up to web standards faster.