You can flip dom.forms.select.customstyling to true in about:config to see how it behaves with and without styling.

The problem is that I have no control over what browsers or operating systems my customers have. I CANNOT ask them to flip a switch deep in the bowels of Firefox.

You points appear to have been replied to in the bug. This issue has certainly not been sat on for seven years.

Bug 1406865 was opened on 9 October 2017. That is **six and a half years ago**. It is still open and unassigned.

On 14 March 2018 another user comment "This is really bad and it's a side effect from the e10s, before that it worked perfectly. Is there a plan to get this fixed in the near future?"

Emilio Cobos Alvarez on 21 Jan 2022 "But given we support it on macOS and Windows yeah, it seems not very objectionable." IMHO that demonstrates **prejudice** on the part of this individual. It may not seem objectionable to him, but is objectionable to others. I appreciate that Linux is chaotic compared to the regimented Apple and Microsoft products, but I do not understand why when I explicitly set styles for an <option> tag, unlike all other tags that I have tried, the styles are ignored if the browser is running on LInux.

The only useful comments have been to point to one of the internal settings of Firefox which re-enables the feature. I appreciate that Emilio Cobos Alvarez tried this and found the support was still flawed, and therefore he did not want to change the default for Linux that formatting is **intentionally** disabled until the capability was improved.

How can I **constructively** address this issue?

Even within the last six and half years, this bug has not gone ignored, as you have seen from the bug report. Indeed, there has been an update to the bug within the last week that I hope you have seen.

To constructively progress this:

Please stop calling out particular Mozillians. We are all doing our best to help with varying degrees of understanding of both the immediate and the longer term picture.

Please appreciate that Firefox is developed for free by a small team of staff and many volunteers working across many platforms. There are going to be times when understandings of priorities is going to differ.

Give me the opportunity to follow up with staff directly and come back to you here. This will not take seven or even six and half years, but I hope to get you an update within a week.

Thank you.

Note that Bugzilla is not a forum as it is a general issues tracker. In fact https://www.bugzilla.org is a tracker that Mozilla makes for companies, organizations, and projects to use to track a whole variety of things.

Also your comments on the two bugs were made hidden due to breaking etiquette. https://bugzilla.mozilla.org/page.cgi?id=etiquette.html

This site is a Support Forum and Knowledge Base.

Also this forum has its own guidelines. https://support.mozilla.org/en-US/kb/mozilla-support-rules-guidelines

Who is this **clerk** to override the fact that a number of customers very much find this "objectionable".

Being a customer implies you paid for the Firefox web browsers when it is 100% free to download and use. You can even build Firefox from source yourself for desktop and Android.

Mozilla does have some subscription based products (like Mozilla VPN) that you can get direct support for though.

If you want a bug in bugzilla.mozilla.org to be fixed then submit a patch for it to either be fixed or get ball rolling to being fixed at least. Seen this happen lots of times.

Hi James

As mentioned previously, I am following up on the points that you have recently raised further to discussion with Mozilla staff.

As you are very aware, it is not the case that nothing has been happening with the issue that you have raised in our bug tracking system. In fact for both of the bugs that you have raised, staff have looked into them and have progressed them. What has not happened is that progress has not been as fast as you want. The challenge that we have is that the issue is a fair bit more complex then may first appear.

Wanting to specify a foreground and background colour for a select drop down does avoid some of the challenges in managing background colours across different operating systems, but is it also not easy to make it just work for your use case without supporting other use cases where only one colour is specified.

This is a lot of work for us to resolve and may cause breakage for some users and some sites. While you may see this in place on Windows, it is not yet available for macOS, some mobile platforms and Linux (made more challenging by the wide range of desktops available for Linux).

While you are looking for a solution for your situation, we need to be able implement a solution that covers multiple eventualities while at the same time being fair to all and efficient to put in place.

As mentioned earlier, this work is ongoing but please appreciate that it may not be the highest priority. I am a Linux user myself and this issue does not stop me from having a great experience using the web in Firefox. I feel comfortable to go out on a limb and suggest that many Linux users may not even notice it.

Please can you stop filing multiple support questions here and filing multiple bugs on our bug tracking platform on the same issue. That and your tone towards people trying to find a resolution is not helping you and, if anything, is more likely to see you being removed from these platforms.

I suggest that going forwards this is not a support issue, but an active bug that is being looking into by our developers and contributor community. You will be able to follow progress on this here.

Before making any further comments on any Mozilla platforms, I strongly recommend that you read and consider carefully the Mozilla Community Participation Guidelines and the Bugzilla Etiquette guide.

Thank you.