'Select' element stops working if "browser.tabs.remote.desktopbehavior" is turned off
Categories
(Firefox :: Untriaged, defect)
Tracking
()
People
(Reporter: asdd2808, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0
Steps to reproduce:
Used any select element (the version field in this bug report form, the element in https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_select )
Arrow keys work for selecting options (but some websites will automatically refresh when the option changes)
It is important to note that this issue DOES NOT apply to the select elements used in the Firefox preferences, so some way to force using those would work as a workaround.
On Xfce4 (Ubuntu 20.04.1 LTS Focal Fossa with XFCE4 manually installed, up to date as of Mon 21 Sep 16:43:09 BST 2020 )
(Firefox 80.0.1 as packaged by canonical, aka "firefox/focal-updates,focal-security,now 80.0.1+build1-0ubuntu0.20.04.1 amd64 [installed]")
This occurs with the compositor disabled or enabled, but I keep the compositor disabled generally.
This occurs in safe mode (activated via help) and outside of safe mode.
This occurs with hardware acceleration enabled or disabled.
Note that similar popups like the top-right menu work perfectly. It's just select elements that have an issue.
Actual results:
All 'select' elements do not show options or any overlay at all when clicked on, or when space or enter is pressed.
Expected results:
It would be possible to actually select.
Update: Nevermind on the 'xfce4' part. It's an issue with something specific to my profile, NOT with the desktop environment (su'ing to another user at least works)
But the thing is it's an issue which still applies when safe mode is active. Need to poke further.
So the answer is that "browser.tabs.remote.desktopbehavior" is a weird flag which breaks things if turned off.
...In case anyone asks why I turned off "browser.tabs.remote.desktopbehavior" in the first place, keep in mind Firefox uses approximately 22% of my RAM. At the time I was probably trying as hard as I could to disable multiprocess. P.S. Please add a button to disable multiprocess.
As for why I wanted to disable multiprocess in the first place, well, as an example, take disabling "browser.tabs.remote.separatePrivilegedContentProcess" and "browser.tabs.remote.separatePrivilegedMozillaWebContentProcess".
With these on, my total RAM usage is 33.3%. Off, 34.5%. That's around ~44.8MB.
Description
•