The Tab Queue item is removed from the notification panel on update

RESOLVED WONTFIX

Status

()

Firefox for Android
General
RESOLVED WONTFIX
3 years ago
3 years ago

People

(Reporter: Caspy7, Unassigned)

Tracking

(Blocks: 1 bug)

unspecified
Points:
---

Firefox Tracking Flags

(fennec-)

Details

(Reporter)

Description

3 years ago
I updated my Beta this morning and lost the tab queue that was sitting in the notifications area.
There was only one tab in it, but there could have been more. Either way it definitely falls into the dataloss category (I still don't recall what was in it).
tracking-fennec: --- → ?
(In reply to Caspy7 from comment #0)
> I updated my Beta this morning and lost the tab queue that was sitting in
> the notifications area.

Is just the notification gone but the tab is still opened the next time you open the app? Or is the URL/tab completely gone?
(Reporter)

Comment 2

3 years ago
It does appear that the tab opened when I opened the browser. So I guess the issue then is that the tab queue item is being removed from the notifications panel - giving the appearance of dataloss.
Summary: The Tab Queue is lost on update (dataloss) → The Tab Queue item is removed from the notification panel on update
I don't think there's anything we can do about that -- IIRC an upgrade involves a force-stop of the process, and when a process is killed its notifications are removed from the notification center.

We could re-create the notification next time we are non-foreground running and see there are queued tabs, but this seems like an edge case to me: most users update every six weeks or longer on release, so this shouldn't happen often, and the easiest way to get the process running again is to… launch the browser, which will open the queued tab anyway.
(Reporter)

Comment 4

3 years ago
Closing as wontfix as it appears we may not be able to remedy the situation technically - or that it wouldn't be worth the effort.

Mark otherwise if you feel otherwise.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX

Comment 5

3 years ago
(In reply to Caspy7 from comment #4)
> Closing as wontfix as it appears we may not be able to remedy the situation
> technically - or that it wouldn't be worth the effort.

I agree, I don't think it's worth the effort.

But thanks for filing, we appreciate bug reports!
tracking-fennec: ? → -
You need to log in before you can comment on or make changes to this bug.