Create an about:config pref to set the user agent string to 100. true/false
Categories
(Web Compatibility :: Tooling & Investigations, task, P3)
Tracking
(firefox-esr91 wontfix, firefox95 wontfix, firefox96 wontfix, firefox97 wontfix, firefox98 fixed)
People
(Reporter: karlcow, Assigned: cpeterson)
References
Details
Attachments
(3 files, 1 obsolete file)
(based on a proposal by Chris Peterson)
To help devs test their website with version/100, we should probably give an about:config pref to flip and set version 100
Chrome has a setting UI in chrome://flags/#force-major-version-to-100
Some risks:
- What is happening if the person has already manually changed the UA string?
- What is happening if the person has used an addon for changing the UA string?
Some thoughts
- When Firefox actually reached 100, we need to remove the feature. So we could open a second bug to remove it.
Other possibilities
- Specific Addon to install
- add a "Test Firefox Version 100" checkbox to Firefox Nightly's "Experiments" settings? about:preferences#experimental (proposed also by Chris)
| Assignee | ||
Comment 1•4 years ago
|
||
I have a patch.
| Assignee | ||
Comment 2•4 years ago
|
||
This pref makes Firefox send websites a User-Agent string that pretends to be Firefox version 100. Web developers can use this setting to test whether websites will break when Firefox hits a three-digit version number. The real Firefox 100 is scheduled to be released in May 2022.
Chrome has a similar chrome://flags/#force-major-version-to-100 flag for testing a Chrome 100 UA.
| Assignee | ||
Comment 3•4 years ago
|
||
This pref makes Firefox send websites a User-Agent string that pretends to be Firefox version 100. Web developers can use this setting to test whether websites will break when Firefox hits a three-digit version number. The real Firefox 100 is scheduled to be released in May 2022.
Chrome has a similar chrome://flags/#force-major-version-to-100 flag for testing a Chrome 100 UA.
Depends on D135315
| Assignee | ||
Comment 4•4 years ago
|
||
Comment 7•4 years ago
|
||
| bugherder | ||
Comment 10•4 years ago
|
||
Backed out 3 changesets (Bug 1748798) for causing bc test failures on browser_navigator.js.
Backout link
Push with failures
Failure Log
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Comment 11•4 years ago
|
||
Comment 12•4 years ago
|
||
Comment 13•4 years ago
|
||
Backed out for causing mochitest failures on browser_navigator.js
- Backout link
- Push with failures
- Failure Log
- Failure line: TEST-UNEXPECTED-FAIL | browser/components/resistfingerprinting/test/browser/browser_navigator.js | Checking forceVersion100 navigator.userAgent. - Got "Mozilla/5.0 (Windows NT 10.0; rv:100.0) Gecko/20100101 Firefox/100.0", expected "Mozilla/5.0 (Windows NT 6.1; rv:100.0) Gecko/20100101 Firefox/100.0"
Comment 14•4 years ago
|
||
Comment 15•4 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/68668619bf9a
https://hg.mozilla.org/mozilla-central/rev/18d5cb739f09
Comment 16•4 years ago
|
||
Description
•