Open Bug 1961638 Opened 21 days ago Updated 6 days ago

When choosing "Exit" from menu, Firefox "keeps running" and "reopening" does not trigger "runtime.onStartup"

Categories

(Firefox for Android :: WebExtensions, defect)

All
Android
defect

Tracking

()

People

(Reporter: Manuel.Spam, Unassigned, NeedInfo)

Details

Steps to reproduce

I guess the simplest option to reproduce is to use USB debugging

  1. Make sure you have Firefox for Android configured to clear private settings on Exit (which will enable the "Exit" option in the menu)
  2. Enable USB debugging in Firefox for Android
  3. Connect to this Firefox instance from any Desktop Firefox
  4. Open "about:debugging" and scan for devices. "Firefox" should be found.
  5. If you close Firefox from the list of "recently used apps", then the Entry "Firefox" disappears on "about:debugging".
  6. If you close Firefox from the "Exit" entry in the menu, then the Entry "Firefox" will not disappear but connecting seems to fail (probably the App is just suspended but not really exited)

Expected behavior

Firefox should exit if I use the "Exit" menu entry. If that's not possible for some reason, then at least there should be some workaround established which makes the "onStartup" event being called so Add-ons can actually re-initialize itself if the user "re-opens" Firefox after exiting.

Actual behavior

The user "thinks" he reopens Firefox but Add-ons don't get the required events.

Device information

  • Firefox version: 137.0.2
  • Android device model: Pixel 6a
  • Android OS version: 15

Any additional information?

https://github.com/M-Reimer/cookiewhitelist/issues/1
The problem is that my Add-on wants to clear unwanted cookies but can't as there is no event which tells my Add-on that Firefox has been restarted after "exiting" from the menu.

The severity field is not set for this bug.
:towhite, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(towhite)
You need to log in before you can comment on or make changes to this bug.