Closed Bug 1032122 Opened 10 years ago Closed 10 years ago

[Vertical Homescreen] Statusbar not opaque when opening a dialog in verticalhome to remove apps/bookmarks/collections

Categories

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

Product:
Firefox OS Graveyard
Component:
Gaia::Homescreen
Platform:
All
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(blocking-b2g:2.0+, b2g-v2.0 verified, b2g-v2.1 verified)

Status:
VERIFIED FIXED
Milestone:
2.0 S5 (4july)
Project Flags:
blocking-b2g 2.0+
Tracking Flags:
Tracking Status
b2g-v2.0 --- verified
b2g-v2.1 --- verified

People

(Reporter: crdlc, Assigned: crdlc)

References

Details

(Whiteboard: [systemsfe])

Attachments

(2 files)

Github pull request
(deleted), text/html
vingtetun
: review+
Details
verified_V2.1.png
(deleted), image/png
Details
Steps to reproduce: Unlock the screen of the phone, get on the vertical homescreen, long touch an app on the screen to enter in edit mode and try to remove an app/bookmark/collection. Actual results: The dialog opens, but the status bar remains transparent. Expected results: the status bar should become opaque like context menu does (bug 1028708)
Assignee: nobody → crdlc
Status: NEW → ASSIGNED
Blocks: vertical-home-next
Whiteboard: [systemsfe]
Attached file Github pull request (deleted) —
Thanks Vivien for your time
Attachment #8447903 - Flags: review?(21)
Comment on attachment 8447903 [details] Github pull request LGTM.
Attachment #8447903 - Flags: review?(21) → review+
Blocks: 1015336
No longer blocks: vertical-home-next
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking?]
Per a discussion with VD - all instances of a transparent status bar appearing when it shouldn't is a blocker for the 2.0 visual refresh.
blocking-b2g: 2.0? → 2.0+
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking?] → [VH-FL-blocking-][VH-FC-blocking+]
Target Milestone: --- → 2.0 S5 (4july)
Stepping in to press the button to merge button so we get a better view of our current blocker status. Thanks guys. https://github.com/mozilla-b2g/gaia/commit/d8aa2da456308e1df3d43b6a3268a8933ef6bf3d
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
This issue has been successfully verified on Flame v2.1&2.0. See attachment: verified_v2.1.mp4 Reproduce rate: 0/5 Flame 2.1 build: Gaia-Rev ccb49abe412c978a4045f0c75abff534372716c4 Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/18fb67530b22 Build-ID 20141202001201 Version 34.0 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20141202.034824 FW-Date Tue Dec 2 03:48:34 EST 2014 Bootloader L1TC00011880 Flame 2.0 build: Gaia-Rev 8d1e868864c8a8f1e037685f0656d1da70d08c06 Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/c756bd8bf3c3 Build-ID 20141202000201 Version 32.0 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20141202.034707 FW-Date Tue Dec 2 03:47:18 EST 2014 Bootloader L1TC00011880
Status: RESOLVED → VERIFIED
status-b2g-v2.0: fixed → verified
status-b2g-v2.1: fixed → verified
Attached image verified_V2.1.png (deleted) —
Sorry to update comment 6 > See attachment: verified_v2.1.mp4 ->See attachment: verified_v2.1.png
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: