Closed Bug 1028708 Opened 10 years ago Closed 10 years ago

statusbar not opaque when opening the contextMenu in verticalhome

Categories

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

defect
Not set
normal

Tracking

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

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

People

(Reporter: inscription, Assigned: inscription)

References

Details

(Whiteboard: [systemsfe])

Attachments

(1 file, 2 obsolete files)

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release) Build ID: 20140428194215 Steps to reproduce: Unlock the screen of the phone, get on the vertical homescreen, long touch an empty space on the screen to open the context menu. Actual results: The context menu opens, but the status bar remains transparent. Expected results: the status bar should become opaque.
Attachment #8444121 - Flags: review?(kgrandon)
Attachment #8444121 - Attachment is obsolete: true
Attachment #8444121 - Flags: review?(kgrandon)
Attachment #8444122 - Flags: review?(kgrandon)
Comment on attachment 8444122 [details] [diff] [review] statusbar not opaque when opening the contextMenu in verticalhome. Review of attachment 8444122 [details] [diff] [review]: ----------------------------------------------------------------- Cristian - Could you review this one for me? Thanks!
Attachment #8444122 - Flags: review?(kgrandon) → review?(crdlc)
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking-]
Comment on attachment 8444122 [details] [diff] [review] statusbar not opaque when opening the contextMenu in verticalhome. Review of attachment 8444122 [details] [diff] [review]: ----------------------------------------------------------------- LGTM although where is the context-menu-open dispatched? I haven't seen it, please let me know if you missed it or I couldn't see it in the patch. Thanks
Attachment #8444122 - Flags: review?(crdlc)
Ah right, I guess we added this for some smart collections work: https://github.com/mozilla-b2g/gaia/blob/master/apps/verticalhome/js/contextmenu_ui.js#L30 (Needed to know the position to insert smart collections)
Comment on attachment 8444122 [details] [diff] [review] statusbar not opaque when opening the contextMenu in verticalhome. Review of attachment 8444122 [details] [diff] [review]: ----------------------------------------------------------------- ok, so r+
Attachment #8444122 - Flags: review+
The patch to land (with Kevin Canévet) as an author). Fixed a small nit as there was a bug when the homescreen was scrolled to the top, the edit mode was on, and a contextmenu was popped up. The bug was that in edit mode you can have a transparent statusbar.
Attachment #8444122 - Attachment is obsolete: true
Attachment #8444373 - Flags: review?(crdlc)
Comment on attachment 8444373 [details] [diff] [review] bug1028708.patch (to check-in) Review of attachment 8444373 [details] [diff] [review]: ----------------------------------------------------------------- LGTM although I guess that we should do it how the old homescreen worked. I mean we should disable the contexmenu feature while we are in edit mode here https://github.com/mozilla-b2g/gaia/blob/master/apps/verticalhome/js/contextmenu_handler.js#L21 if (this.canceled || app.grid._grid.dragdrop.inEditMode) { return; }
Attachment #8444373 - Flags: review?(crdlc) → review+
(In reply to Cristian Rodriguez (:crdlc) from comment #8) > Comment on attachment 8444373 [details] [diff] [review] > bug1028708.patch (to check-in) > > Review of attachment 8444373 [details] [diff] [review]: > ----------------------------------------------------------------- > > LGTM although I guess that we should do it how the old homescreen worked. I > mean we should disable the contexmenu feature while we are in edit mode here > https://github.com/mozilla-b2g/gaia/blob/master/apps/verticalhome/js/ > contextmenu_handler.js#L21 > > if (this.canceled || app.grid._grid.dragdrop.inEditMode) { > return; > } I tend to think like you but I don't really know if this behavior is expected or not.
or disable contexmenu handler when it receives the gaiagrid-editmode-start and restore its behavior when it receives gaiagrid-editmode-end instead of checking app.grid._grid.dragdrop.inEditMode I think that it should work so because the context menu does not make sense in edit mode IMHO I saw that jsavory added the interaction design document, do you know if this is the expected behavior?
Flags: needinfo?(jsavory)
Whiteboard: [systemsfe]
In a separate bug UX clarified that all instances of the transparent status bar should block the visual refresh for 2.0, so marking this as a blocker.
Status: UNCONFIRMED → NEW
blocking-b2g: 2.0? → 2.0+
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking-] → [VH-FL-blocking-][VH-FC-blocking+]
Ever confirmed: true
Blocks: 1015336
Assignee: nobody → 21
Sorry Cristian, I'm not sure I completely understand the question. Could you explain the behaviour you are referring to?
Flags: needinfo?(jsavory) → needinfo?(crdlc)
OK, you are in the vertical homescreen and you enter in edit mode: Does contexmenu feature make sense in this scenario? In the old homescreen when you were in edit mode the contextmenu to set wallpaper or add a new smart collection was disabled. IMHO we should follow the same approach thought. Contextmenu feature only for normal mode instead of edit mode too
Flags: needinfo?(crdlc) → needinfo?(jsavory)
Target Milestone: --- → 2.0 S5 (4july)
(In reply to Cristian Rodriguez (:crdlc) from comment #13) > OK, you are in the vertical homescreen and you enter in edit mode: Does > contexmenu feature make sense in this scenario? In the old homescreen when > you were in edit mode the contextmenu to set wallpaper or add a new smart > collection was disabled. IMHO we should follow the same approach thought. > Contextmenu feature only for normal mode instead of edit mode too I agree - Let's stick the the previous behaviour and disable the context menu while in edit mode.
Flags: needinfo?(jsavory)
I will file a followup to not display the contextmenu in edit mode and provide a patch there. I Would like to land this patch as if, as it comes from a contributor, that may not have the time to fix the followup. https://tbpl.mozilla.org/?tree=Gaia-Try&rev=8249787956debdd02514b5bf3c480125486b2a71
Assignee: 21 → inscription
Status: NEW → ASSIGNED
https://github.com/mozilla-b2g/gaia/commit/6d33e7207146e86586ed49434662b9c1899c0a79 Gaia-Try is green for all the tests related to this. Seems like we have a new perma-red unrelated to this patch though as I can see it on all Gaia-Try results for everybody... I will open the followup soon.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
The original landing on master was pushed with Vivien as the author. At his request, I reverted the original landing and re-pushed it with Kevin as the author. Master: https://github.com/mozilla-b2g/gaia/commit/1f0902c6165297d51883ca6f9fe300bfee1f4c08
For what it worth, the followup I promised is bug 1031331.
Gaia b8f36518696f3191a56e4f33447ee9d6ec820da1 Gecko https://hg.mozilla.org/mozilla-central/rev/9290d7995f98 BuildID 20140627040205 Version 33.0a1 ro.build.version.incremental=109 ro.build.date=Mon Jun 16 16:51:29 CST 2014 Flame
Status: RESOLVED → VERIFIED
Verified on Gaia 8df02268fcd7e80c5fab8c1ec099772e37f8659d Gecko https://hg.mozilla.org/releases/mozilla-aurora/rev/731a5e8831e6 BuildID 20140627000201 Version 32.0a2 ro.build.version.incremental=109 ro.build.date=Mon Jun 16 16:51:29 CST 2014 Flame
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: