Indeed, and this argument ("it will be too bloated") is often used by developers themselves to avoid (or hide) advanced features. I never quite understood it. Just put all the mysterious flags behind an "Advanced" menu, which normie users will know not to touch.

There would still be decidedly fewer complaints, because extensions are vastly easier to manage and disable or remove than this long list of about:config settings. The fact that you cannot satisfy everybody simultaneously cannot be an excuse for failing to ship with sensible defaults and easy, discoverable customization.

They right clicked on an image which is also a clickable link which adds the additional options for both links and images, a total of 11, to the defaults.

Kinda, but if something can be built as an extension, it probably should be. It proves what you can do with the APIs, proves it can be replaced / forked by other people, and ensures a consistent level of isolation by default.

And if it can't... often it's worth asking if it should be possible.