Mozilla on the coming version-100 apocalypse

Posted Feb 17, 2022 23:39 UTC (Thu) by khim (subscriber, #9252)
In reply to: Mozilla on the coming version-100 apocalypse by pabs
Parent article: Mozilla on the coming version-100 apocalypse

Then people would just take Chromium (or Firefox) sources and release version which “works”.

Remember how that happened with Flash last year?

With Flash that was a stop-gap solution because Flash required so many hacks in different parts of browser that it wasn't really practical to forward-port the change.

When you only need to change UA string… that “extra-compatible” browser can be supported for a very long time.

to post comments

Mozilla on the coming version-100 apocalypse

Posted Feb 18, 2022 10:20 UTC (Fri) by rqosa (subscriber, #24136) [Link] (1 responses)

> When you only need to change UA string…

Aren't there simpler ways to accomplish that than recompiling the browser from source (which, if used by end-users outside of an intranet managed by an IT department, would presumably also require the end-users to download & install the resulting "alternate version" of the browser)? Such as: using Firefox's "general.useragent.override" setting in about:config, or using a Chrome extension or a Firefox add-on.

Mozilla on the coming version-100 apocalypse

Posted Feb 18, 2022 13:59 UTC (Fri) by geert (subscriber, #98403) [Link]

No need to recompile from source, a hex editor is all you need to change the User-Agent string.