Closed Bug 941174 Opened 12 years ago Closed 12 years ago

[User Story] Browser Chrome: Back/Forward

Categories

(Firefox OS Graveyard :: Gaia::System::Browser Chrome, defect)

Product:
Firefox OS Graveyard
Component:
Gaia::System::Browser Chrome
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(feature-b2g:2.1)

Status:
RESOLVED FIXED
Milestone:
2.1 S3 (29aug)
Project Flags:
feature-b2g 2.1

People

(Reporter: pdol, Assigned: vingtetun)

References

Details

(Whiteboard: [ucid:System124, 1.4:P2, ft:systems-fe], system-browser, [p=2][systemsfe][tako])

User Story: As a user I want to navigate back to the last/forward to the next page in session history so that I can easily get back to pages that I just visited. Acceptance Criteria: Functionality should match existing Browser functionality unless described otherwise in UX spec.
Blocks: browser-chrome-mvp
Component: Gaia::System → Gaia::System::Browser
No longer blocks: browser-chrome-mvp
Blocks: browser-chrome-mvp
Estimating as 2 points.
Whiteboard: [ucid:System124, 1.4:P2, ft:systems-fe], system-browser → [ucid:System124, 1.4:P2, ft:systems-fe], system-browser, [p=2]
Blocks: 1.4-systems-fe
Flags: in-moztrap?(nhirata.bugzilla)
No longer blocks: 1.4-systems-fe
Ideally we'd like back/forward to be part of the new unified chrome for user testing.
Blocks: 992926
QA Contact: bfrancis
WIP patch, hopefully good enough for user testing https://github.com/benfrancis/gaia/commit/33fea86748e5233390339560a3b90ea0b003e9a9
Assignee: nobody → bfrancis
QA Contact: bfrancis
Target Milestone: --- → 2.0 S1 (9may)
Whiteboard: [ucid:System124, 1.4:P2, ft:systems-fe], system-browser, [p=2] → [ucid:System124, 1.4:P2, ft:systems-fe], system-browser, [p=2][systemsfe]
feature-b2g: --- → 2.1
Hey Ben whats the state on this? I would like to implement overflow / options as not being able to save to homescreen is doing my head in, should we split this out?
Flags: needinfo?(bfrancis)
Yeah sorry, it got de-prioritised after 2.0 blockers. Let me try and get this is a state where it can be landed. We should definitely split out the overflow menu button as that was just a dummy button requested by UX, but I would prefer to land this before the overflow menu and before bug 941035 as it adds similar "currentApp" code.
Flags: needinfo?(bfrancis)
Target Milestone: 2.0 S1 (9may) → 2.0 S2 (23may)
Target Milestone: 2.0 S2 (23may) → ---
blocking-b2g: --- → backlog
blocking-b2g: backlog → ---
Whiteboard: [ucid:System124, 1.4:P2, ft:systems-fe], system-browser, [p=2][systemsfe] → [ucid:System124, 1.4:P2, ft:systems-fe], system-browser, [p=2][systemsfe][tako]
Target Milestone: --- → 2.1 S1 (1aug)
Looks like Vivien is working on this in bug 1039519, not much point in it being assigned to me. https://bugzilla.mozilla.org/show_bug.cgi?id=1039519#c22
Assignee: bfrancis → 21
Target Milestone: 2.1 S1 (1aug) → 2.1 S2 (15aug)
Ben - anything you can think of that's left to do here? Can we close this for acceptance testing?
Flags: needinfo?(bfrancis)
Depends on: 1056770
I think the only part of the spec left to implement is the transition of Rocketbar size when the back and forward buttons appear/disappear. I filed bug 1056770 for that.
Target Milestone: 2.1 S2 (15aug) → 2.1 S3 (29aug)
No longer depends on: 1056770
Ready for QA on core functionality. Transition to be handled separately in bug 1056770.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Flags: needinfo?(bfrancis)
You need to log in before you can comment on or make changes to this bug.