Closed Bug 1041371 Opened 6 years ago Closed 6 years ago

[User Story] Rocketbar behavior for fullscreen apps without navigation chrome

Categories

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

x86
macOS
defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED
2.1 S3 (29aug)

People

(Reporter: pdol, Assigned: vingtetun)

References

Details

(Keywords: feature, Whiteboard: [ucid:System235], [systemsfe][tako])

User Story

This bug is to match the Rocketbar behavior for fullscreen apps without navigation chrome to the UX spec

Acceptance Criteria:
1. The interaction and visual design for the Rocketbar for fullscreen apps without navigation chrome matches the UX spec
No description provided.
blocking-b2g: backlog → ---
Whiteboard: [ucid:System235], [ft:systemsfe] → [ucid:System235], [systemsfe][tako]
Target Milestone: --- → 2.1 S1 (1aug)
Assignee: nobody → chrislord.net
Assignee: chrislord.net → 21
Target Milestone: 2.1 S1 (1aug) → 2.1 S2 (15aug)
Flags: in-moztrap?(mozillamarcia.knous)
Peter, I'm not sure how useful this bug and bug 1041372 and bug 1041373 and bug 1041376 are. They're not really user stories as such.

Can we try to identify specific issues that need addressing and either use these as meta bugs or file bugs blocking the existing user stories in System::Browser Chrome?
Flags: needinfo?(pdolanjski)
(In reply to Ben Francis [:benfrancis] from comment #1)
> Peter, I'm not sure how useful this bug and bug 1041372 and bug 1041373 and
> bug 1041376 are. They're not really user stories as such.
> 
> Can we try to identify specific issues that need addressing and either use
> these as meta bugs or file bugs blocking the existing user stories in
> System::Browser Chrome?

Sure.  Let's use these as meta bugs.
feature-b2g: 2.1 → ---
Depends on: 1050868
Flags: needinfo?(pdolanjski)
Target Milestone: 2.1 S2 (15aug) → 2.1 S3 (29aug)
I think we can close this. Any remaining work is tracked by other dependencies of bug 945259.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.