Incorrect. If Firefox had not put it in, nothing would have happened because programmers have (largely) decided to give chrome a majority market-share amongst them, and advocate it to their non-technical peers, increasing its market share amongst that group as well.
If programmers actually used firefox and advocated it to the point where it had a majority market share then maybe their refusal would carry some weight.
But as it stands the web dev community has said loud and clear what their priorities are, and this is just a natural consequence of that.
I used to make an effort to use FF, but it gradually got slower, froze up more often, had problems with content I was viewing.
The final straw was when they had a big update. Instead of fixing any of these issues, they gave me the ability to call people with service I don't use by clicking a link :/
Similar boat here. I abandoned Firefox back in the day due to the memory and freezing problems, and general lack of responsiveness compared to Chrome. The difference in everyday use was massive here; we went from having a browser that could hardly handle having 3 tabs open while using a gigabyte of memory, to one that worked flawlessly and used a fraction of the resources. Firefox then put in a lot of effort fixing those issues. By this time though, Chrome's built-in DevTools was more robust for my tastes compared to Firebug or the horrific early versions of their built-in replacement. I had a good development setup, all the addons I needed, and a fast browser. I simply had little reason to switch back.
I did spend a brief period swapping back to Firefox for the sake of perceived privacy, but then they started bundling all sorts of third party bloatware and it was just too much. I'm not a superfan of the information I imagine Google collects from my using Chrome, but the browser itself is just too good to give up. Firefox now only gets opened to verify cross-browser functionality of frontend UIs I work on, and on rare occasions when I want to use a proxy in a browser without it being used system-wide.
I personally think that firefox got a lot better recently. I've been using ff dev since it launched, and it's been pretty good. And in speed tests, it's started to beat Chrome, although things may have since reversed.
I also use FF in day-to-day both due to privacy concerns and general fitness for my style, but chrome's dev tools are objectively superior, you have to face it...
Browser can be either better technically, or you might have valency for certain design decisions.
If there is a browser vendors that claims certain social values, but is constantly failing to execute them in the design, you might as well just use the technically better one that does not pretend to protect the values you consider worth protecting. You will be spared of the constant disappointment.
When it was launched, Chrome/Chromium had 2 advantages over Firefox: Speed and superior developer tools.
Chrome was unbelievably quick: the moment you clicked on the launcher and browser 'chrome' (heh) appeared instantaneously, Firefox was comparatively sluggish, and notoriously memory hungry (though that might have been the fault of sloppily written plugins)
If programmers actually used firefox and advocated it to the point where it had a majority market share then maybe their refusal would carry some weight.
But as it stands the web dev community has said loud and clear what their priorities are, and this is just a natural consequence of that.