Closed
Bug 1028685
Opened 10 years ago
Closed 10 years ago
[Collection app] Edit header obscured
Categories
(Firefox OS Graveyard :: Gaia::Everything.me, defect)
Tracking
(blocking-b2g:2.0+, b2g-v2.0 verified, b2g-v2.1 verified)
People
(Reporter: ranbena, Assigned: crdlc)
References
Details
(Whiteboard: [systemsfe])
Attachments
(3 files)
When in Collection edit mode, the edit header doesn't appear.
It seems to be obscured by a higher zIndexed header element.
STR:
1. Open any Smart Collection.
2. Enter edit mode (long press a pinned app)
Expected: Edit mode header fades in.
Actual: Not there.
Reporter | ||
Updated•10 years ago
|
Blocks: vertical-homescreen
Comment 1•10 years ago
|
||
We need a screenshot of the bug here.
Reporter | ||
Comment 2•10 years ago
|
||
In the screenshot it's apparent that the edit mode header isn't visible in edit mode.
Terribly sorry for the poor quality of the screenshot. I'm having trouble taking them from the device.
Comment 3•10 years ago
|
||
(In reply to Ran Ben Aharon (Everything.me) from comment #2)
> Created attachment 8444115 [details]
> Screenshot.jpg
>
> In the screenshot it's apparent that the edit mode header isn't visible in
> edit mode.
>
> Terribly sorry for the poor quality of the screenshot. I'm having trouble
> taking them from the device.
Ah I understand the bug now. Are the icons animating when edit mode is active? If there's no visual indicator, then this is a blocker. If there's at least something there, then I don't think it's a blocker.
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → crdlc
Status: NEW → ASSIGNED
Reporter | ||
Comment 5•10 years ago
|
||
Comment on attachment 8444263 [details]
Github pull request
Yep!
Attachment #8444263 -
Flags: review?(ran) → review+
Reporter | ||
Comment 6•10 years ago
|
||
Jason, imo this is a blocker, since the home button doesn't work as expected, the "done" button is crucial for UX. See Kevin's comment https://bugzilla.mozilla.org/show_bug.cgi?id=1025963#c15
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(jsmith)
Updated•10 years ago
|
blocking-b2g: --- → 2.0?
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking?] → [VH-FL-blocking-][VH-FC-blocking+]
Flags: needinfo?(jsmith)
Keywords: qawanted
Assignee | ||
Comment 7•10 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Target Milestone: --- → 2.0 S4 (20june)
Updated•10 years ago
|
blocking-b2g: 2.0? → 2.0+
Comment 8•10 years ago
|
||
status-b2g-v2.0:
--- → fixed
status-b2g-v2.1:
--- → fixed
This issue has been successfully verified on Flame 2.0:
Gaia-Rev 8d1e868864c8a8f1e037685f0656d1da70d08c06
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/c756bd8bf3c3
Build-ID 20141201000201
Version 32.0
Device-Name flame
FW-Release 4.4.2
This issue has been successfully verified on Flame 2.1:
Gaia-Rev ccb49abe412c978a4045f0c75abff534372716c4
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/18fb67530b22
Build-ID 20141201001201
Version 34.0
Device-Name flame
FW-Release 4.4.2
You need to log in
before you can comment on or make changes to this bug.
Description
•