Closed
Bug 1165892
Opened 9 years ago
Closed 4 years ago
Tab Queue: Prompt to enable after a few external links opened in short amount of time
Categories
(Firefox for Android Graveyard :: Overlays, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: mhaigh, Unassigned)
References
Details
Tab queue is really useful in certain situations, when you're opening a load of links from another application, but is less useful if you just want to open one link as the number of clicks to open the link doubles. It'd be good if we could add another stage to tab queue, neither on or off but perhaps "intelligent" or "detect" which would activate when you've opened a couple of links and then prompt you to enable TQ. The way I imagine it working is that once enabled it would then stay enabled until you next open firefox at which point the original link handling functionality would take over again.
Reporter | ||
Updated•9 years ago
|
Blocks: tab-queue-v2
Comment 1•9 years ago
|
||
Another way to think about this: make those two taps really easy. Most of the inconvenience now lies in having to shift focus to tap "open now", which might have disappeared by the time you remember that tab queue is on (as opposed to your phone being slow!). One way to do this is to have a big round tap target appear directly over the link you tapped, perhaps with a radial timer. If you scroll or wait for a second or two, it goes away; if you tap it, it opens the link immediately. This is basically an affordance for a reflexive double-tap behavior. The existing toast sticks around for the slowcoaches. I feel that this is preferable to having a flip-flopping mode; with flip-flopping, I feel like I'd be annoyed half the time because I'd just opened Firefox, so the first few links I open from Feedly switch activities… and then annoyed the other half of the time because I have to click "open now" just because I'd queued something!
Updated•9 years ago
|
Component: General → Overlays
Reporter | ||
Updated•9 years ago
|
Assignee: mhaigh → nobody
Comment 2•4 years ago
|
||
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: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•