[Bug] Can't open addon settings if different useragent string is set on Firefox Android Beta
See original GitHub issueBug Report
Bug Description
When a different useragent string is set, the addon settings are not accessible.
Steps To Reproduce
Set a different useragent string on Firefox Android Beta (open about:config
, create a string-entry with the title general.useragent.override
and an Chrome useragent string as content, like Mozilla/5.0 (Linux; Android 10; POCOPHONE F1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Mobile Safari/537.36
), now open the addon settings on any website, the addon settings will show Loading, please wait
and the page will load forever. If the useragent string is reset, the settings are shown again.
Expected Behavior
Show the addon settings
Actual Behavior
The addon settings will show Loading, please wait
and the page will load forever.
System Information
- OS: Android 10
- Browser: Firefox Android Beta 95.0.0-beta.4
- Dark Reader Version: Version 5 Preview 4.9.42 (but this has been going on for a while now…)
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
[Bug] general.useragent.override is not working in Android Beta
Steps to reproduce Open about:config Create general.useragent.override key with custom string as value Expected behavior user-agent header could be changed ...
Read more >How to reset the default user agent on Firefox - Mozilla Support
This article explains how to fix problems with your Firefox user agent so that websites work properly.
Read more >933959 - general.useragent.override.[domain] (about:config ...
[domain] set user agent string for specific domain. But it doesn't work in Firefox 25. Only general override (general.useragent.override, without domain) ...
Read more >I need to change Operating System detected via JavaScript
I used browserspy(http://browserspy.dk/os.php) to see my OS detected via JavaScript (OS CPU detected via JavaScript:Windows NT 6.1; WOW66 ).
Read more >Remove support for appending arbitrary data to the User ...
Gecko allows third-parties to append data to the UA string by setting general.useragent.extra.* prefs. (Are there other ways?)
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’d like to see this resolved too (using desktop Firefox, happens there too). That config is meant for websites, not browser extensions.
I’ve had a look at those methods and they seem to use a duck test, “If it walks like a duck, sounds like a duck, acts like a duck, it must be a duck”, which can be very inconsistent between versions and future versions of browsers, as most of these are relying on experimental features, which come and go between releases. UA is currently the method to recognize browsers for dark reader as we need to apply workaround and patches for certain applications as it will otherwise not work(hence why you can’t open addon settings).
Note: It’s really shooting yourself in the foot by using a completely other browser user-agent than the current browser. I’d recommend to use a Addon to do this(which can’t conflict to Dark Reader).