Open Bug 1946930 Opened 2 months ago Updated 1 month ago

Do not break ForceBindIP support on every update

Categories

(Toolkit :: Application Update, enhancement)

Product:
Toolkit
Component:
Application Update
Version:
Firefox 135
Type:
enhancement

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: i3v, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:135.0) Gecko/20100101 Firefox/135.0

Steps to reproduce:

I've created a ForceBindIP-based launcher shortcut for my Firefox. It worked OK for a while. At some point, it got broken without any warning.

Actual results:

I only use Firefox with ForceBindIP (see https://r1ch.net/projects/forcebindip , https://github.com/ixjb94/ForceBindIP-Gui ). Firefox only works correctly with ForceBindIP if browser.launcherProcess.enabled = False.

By default, Firefox tends to update itself once in a while. Each update resets browser.launcherProcess.enabled, which is "by design" they say ( 1684223 , 1611600 ).

Expected results:

Firefox should be more user-friendly to ForceBindIP users.

It would be great if Firefox would work with ForceBindIP out-of-the-box somehow.

  • maybe by correctly passing the "ForceBindIP settings" to child processes
  • maybe by just providing the ForceBindIP functionality internally
  • maybe by providing some "persistent" way to start Firefox. Something that doesn't break on each Firefox update.
Duplicate of this bug: 1946931

The Bugbug bot thinks this bug should belong to the 'Toolkit::Application Update' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Application Update
Product: Firefox → Toolkit

For now, I can only imagine the following two workarounds:

  • Option 1: disable Firefox updates, e.g. via the Windows registry. (Not great option, but it works.)
  • Option 2: create a launcher script for the Firefox+ForceBindIP startup. A script that would set the browser.launcherProcess.enabled in "perf.js" in your Firefox profile before actually starting Firefox. But I'm not sure if this would work just after Firefox would update itself on startup. I suspect that it would be necessary to kill all "firefox.exe" processes after each update and restart Firefox using the launcher script. Thus, it would also be necessary to set updates to "notify". (Which could be annoying and requires to always remember the "update sequence".)
You need to log in before you can comment on or make changes to this bug.