Closed Bug 989857 Opened 11 years ago Closed 11 years ago

[User Story] Vertical Homescreen Default Layout

Categories

(Firefox OS Graveyard :: Gaia::Homescreen, defect, P1)

x86
macOS
defect

Tracking

(feature-b2g:2.0, tracking-b2g:backlog, b2g-v2.0 fixed)

RESOLVED FIXED
2.0 S2 (23may)
feature-b2g 2.0
tracking-b2g backlog
Tracking Status
b2g-v2.0 --- fixed

People

(Reporter: pdol, Assigned: kgrandon)

References

Details

(Keywords: feature, Whiteboard: [ucid:System172, ft:systemsfe, 2.0],[p=0])

User Story

As a user, I want my default homescreen layout to match the Mozilla UX spec so that I have a consistent experience compared to other users.

Acceptance Criteria:
1. Default homescreen layout matches UX spec.
2. Layout includes app grid, status bar and e.me search.

Note: Status bar and e.me search functionality assumed to be equivalent to 1.4 functionality.
No description provided.
User Story: (updated)
Blocks: 993116
Blocks: 993118
No longer blocks: 993116
blocking-b2g: --- → backlog
Whiteboard: [ucid:System172], [ft:systemsfe] → [ucid:System172, ft:systemsfe, 2.0]
I'm going to mark this as p=0 as I think it's just for tracking mostly and more of a meta bug.
Whiteboard: [ucid:System172, ft:systemsfe, 2.0] → [ucid:System172, ft:systemsfe, 2.0],[p=0]
feature-b2g: --- → 2.0
Flags: in-moztrap?(jlorenzo)
Priority: -- → P1
Assignee: nobody → kgrandon
Flags: in-moztrap?(jlorenzo) → in-moztrap+
I think most items are here for the layout that we feel comfortable closing this one. We have a few bugs open still for the search app and statusbar, but I feel that's outside the scope of this bug given the comment, "Status bar and e.me search functionality assumed to be equivalent to 1.4 functionality." Please re-open or file a new bug for anything specific we should look at.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2.0 S2 (23may)
Mass modify - set status-b2g-v2.0 fixed for fixed bugs under vertical homescreen dependency tree.
blocking-b2g: backlog → ---
You need to log in before you can comment on or make changes to this bug.