Closed Bug 1271306 Opened 9 years ago Closed 4 years ago

Clear tab queue when dismissing notification

Categories

(Firefox for Android Graveyard :: General, enhancement)

ARM
Android
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: freaktechnik, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:46.0) Gecko/20100101 Firefox/46.0 Build ID: 20160502172042 Steps to reproduce: I queued a few URLs and then decided I did not want to load them on my phone and dismissed the notification. Actual results: Next time I queued a tab or opened Firefox for Android the previously queued URLs were still in the queue. Expected results: The queue is cleared. This would probably make more sense together with bug 1233461, which would still allow the current dismissing behavior by selecting the notification action.
Depends on: 1243461
I meant bug 1243461 there as a complement, as that makes more sense. I also don't hang on it being on dismissal, it could also be an action. Just a way to actually clear the queue would be nice.
CC: antlam. Clearing the tab queue could be something to consider when enhancing tq.
Blocks: tab-queue-v2
Severity: normal → enhancement
OS: Unspecified → Android
Hardware: Unspecified → ARM
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.