The <select> element can now be customized with CSS

Developers, don't fall for this!

This web API scope creep makes it __harder__ to create and maintain truly independent web browsers.. you have to implement more and more and eventually we arrive at the current state of matters - all non-chromium engines are lagging behind.

Developers will happily use this, then users will notice websites "look better" in chrome and firefox will become even less relevant. Don't.. you can already achieve this without relying on chromium-only APIs.

> and firefox will become even less relevant

No; Firefox can easily afford financially to add this feature. Firefox is already irrelevant; no developer will shed a tear about just blocking Firefox if they refuse to implement. Boycotting won't work either, because boycotts almost never work.

> Firefox is already irrelevant

Did I miss anything?

It’s still not as clumsy and resource intensive (while destroying hardware like disks) like Chrome..

GP means irrelevant in the sense that Firefox's market share is so low that web devs need not test on it or ensure compatibility.

This saddens me, as a Firefox user, but we have Mozilla's inept management to blame for this.

Firefox doesn't have ad measurement and interests sharing built in yet (or am I wrong?) so it is very relevant for me. I would rather use black-and-white selects everywhere rather than having an advertising engine built into the browser.

You are indeed wrong.

https://support.mozilla.org/en-US/kb/privacy-preserving-attr...

That is disappointing. I went into settings to turn this off but it is already turned off and I don't remember whether I did it or my distribution ships Firefox with non-recommended settings. I hope it is the latter so that I don't get disappointed in Linux distributions also.

"Privacy preserving attribution" sounds like "money preserving robbery" (or money preserving tax).