[toolbar redesign] Implement CFR for forward and back navbar buttons
Categories
(Fenix :: Toolbar, task, P1)
Tracking
(firefox130 fixed)
| Tracking | Status | |
|---|---|---|
| firefox130 | --- | fixed |
People
(Reporter: royang, Assigned: tchoh)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Whiteboard: [fxdroid])
Attachments
(2 files)
This is only to implement the CFR for the back/forward on the navigation bar.
Figma
| Reporter | ||
Updated•4 months ago
|
| Reporter | ||
Comment 1•4 months ago
|
||
Experiment Blocking
Updated•4 months ago
|
| Reporter | ||
Comment 2•4 months ago
|
||
| Reporter | ||
Updated•4 months ago
|
Comment 3•3 months ago
|
||
Setting toolbar redesign's Beta experiment blockers to priority P2 until we finish fixing our Nightly blockers.
Comment 5•1 month ago
|
||
Increasing priority to P1 now that we're fixing toolbar phase 1's beta blockers.
Discussed behavior with Aarjav around what triggers it:
https://mozilla.slack.com/archives/C0554F73006/p1720466233106069
Within 5 seconds, if the user does any of the following
- Taps back button 2+ times.
- Taps forward button 2+ times.
- Taps back and forward 2+ times in any order.
This trigger would be satisfied and the CFR would only be shown. The CFR is only shown once irrespective of which action caused the trigger.
Arrow pointing: The arrow should point in between the 2 buttons. I have updated the designs.
Pushed by tchoh@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/3542fe9f15c1 CFR for forward and back navbar buttons r=android-reviewers,Roger
Comment 8•27 days ago
|
||
| bugherder | ||
Comment 10•26 days ago
|
||
Pushed by tchoh@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/dacb0832d9ac updated apostrophe for string translations r=android-reviewers,Roger
Comment 11•26 days ago
|
||
| bugherder | ||
Comment 12•26 days ago
|
||
A patch has been attached on this bug, which was already closed. Filing a separate bug will ensure better tracking. If this was not by mistake and further action is needed, please alert the appropriate party. (Or: if the patch doesn't change behavior -- e.g. landing a test case, or fixing a typo -- then feel free to disregard this message)
Description
•