Closed
Bug 1189941
Opened 9 years ago
Closed 9 years ago
[Homescreen] Icon will move behind header when at the top of the screen
Categories
(Firefox OS Graveyard :: Gaia::Homescreen, defect)
Tracking
(b2g-v2.2 affected, b2g-master affected)
RESOLVED
WONTFIX
People
(Reporter: AdamA, Unassigned)
References
()
Details
(Keywords: regression, Whiteboard: [2.5-Daily-Testing][Spark][Systemsfe])
Attachments
(2 files)
Description:
when a user moves an icon behind the header to make a new group at the top of the screen the icon will move behind the header.
Repro Steps:
1) Update a Aries to 20150731163020
2) Long press on an icon on the homescreen to enter edit mode
3) Hold an icon and move it to the top of the screen
4) Observe icon move behind header
Actual:
The icon moves behind the header
Expected:
It is expected that the whole icon is visible
Environmental Variables:
Device: Aries 2.5 [Full Flash]
Build ID: 20150731163020
Gaia: 8502d07cd7e68da79303471acf64eea48b3dce24
Gecko: ca53d4297f02
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 42.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
Repro frequency: 10/10
See attached: video clip(https://youtu.be/OM9TEERjlmo), logcat
Reporter | ||
Comment 1•9 years ago
|
||
This issue DOES occur on Flame 2.5 and Flame 2.2.
Environmental Variables:
Device: Flame 2.5 [Full Flash]
BuildID: 20150731030207
Gaia: 8502d07cd7e68da79303471acf64eea48b3dce24
Gecko: ca53d4297f02
Gonk: 41d3e221039d1c4486fc13ff26793a7a39226423
Version: 42.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
Device: Flame 2.2 [Full Flash]
BuildID: 20150731032507
Gaia: 8f3749f875c5ed155ccbd630aa2ee4e8bc2a9400
Gecko: f1aefb986403
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
Result:
The icon moves behind the header
--------------------------
This issue DOES NOT occur on Flame 2.1.
Environmental Variables:
Device: Flame 2.1 [Full Flash]
BuildID: 20150724001207
Gaia: 9dba58d18006e921546cec62c76074ce81e16518
Gecko: 41e10c6740be
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 34.0 (2.1)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Result:
The icon remains above the header.
Blocks: Foxfood-papercuts
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.2:
--- → affected
status-b2g-master:
--- → affected
Flags: needinfo?(ktucker)
Keywords: regression
Whiteboard: [2.5-Daily-Testing][Spark][Systemsfe]
Comment 2•9 years ago
|
||
Alison, can you take a look at this please? What is the intended functionality in this case. Is the behavior in 2.1 the correct behavior?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(ashiue)
Keywords: regressionwindow-wanted
Updated•9 years ago
|
QA Contact: jmercado
Comment 3•9 years ago
|
||
The changes for Bug 1078766 seem to have caused this issue.
B2g-inbound Regression Window
Last Working
Environmental Variables:
Device: Flame 2.2
BuildID: 20141103022233
Gaia: 22d918d469725546ab5a28c5c9b94f78877d1b87
Gecko: 62eda4197b3d
Version: 36.0a1 (2.2)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
First Broken
Environmental Variables:
Device: Flame 2.2
BuildID: 20141103023733
Gaia: 22fd0ab3090300972a0ff8c7a08f4ed31f00eeb1
Gecko: 7a27ae9848b4
Version: 36.0a1 (2.2)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
Last Working gaia / First Broken gecko - Issue does NOT occur
Gaia: 22d918d469725546ab5a28c5c9b94f78877d1b87
Gecko: 7a27ae9848b4
First Broken gaia / Last Working gecko - Issue DOES occur
Gaia: 22fd0ab3090300972a0ff8c7a08f4ed31f00eeb1
Gecko: 62eda4197b3d
Gaia Pushlog: https://github.com/mozilla-b2g/gaia/compare/22d918d469725546ab5a28c5c9b94f78877d1b87...22fd0ab3090300972a0ff8c7a08f4ed31f00eeb1
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: regressionwindow-wanted
Comment 4•9 years ago
|
||
Chris, can you take a look at this please? This looks to have been caused by the work done for bug 1078766.
Blocks: 1078766
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(chrislord.net)
Comment 5•9 years ago
|
||
(In reply to KTucker [:KTucker] from comment #2)
> Alison, can you take a look at this please? What is the intended
> functionality in this case. Is the behavior in 2.1 the correct behavior?
In 2.1, icon would not move behind header since 2.1 unable to create group when move icon to top.
Besides, I found that when moving a group up the top, the group would also behind header if they are ready on top.
NI UX if this is original design?
Flags: needinfo?(ashiue) → needinfo?(kcaldwell)
Comment 6•9 years ago
|
||
Should just be a CSS z-index tweak, I'll take a look.
Assignee: nobody → chrislord.net
Status: NEW → ASSIGNED
Flags: needinfo?(chrislord.net)
In the 2.2 UX work for App Grouping:
When dragging an icon or group towards the top of the page, the page should auto-scroll up. If there is a lag in time, the group or icon would go behind the Edit header.
NI'ing Chris - I don't think this is a z-index thing - correct?
Flags: needinfo?(kcaldwell) → needinfo?(chrislord.net)
Comment 8•9 years ago
|
||
(In reply to katieC from comment #7)
> In the 2.2 UX work for App Grouping:
> When dragging an icon or group towards the top of the page, the page should
> auto-scroll up. If there is a lag in time, the group or icon would go behind
> the Edit header.
>
> NI'ing Chris - I don't think this is a z-index thing - correct?
Sounds like z-index to me. I've assigned this to myself, but it's quite low priority what with the new homescreen work. Let me know if it needs to be bumped up, I don't anticipate it being a big job.
Flags: needinfo?(chrislord.net)
Comment 9•9 years ago
|
||
Unassigning now that verticalhome isn't the default.
Assignee: chrislord.net → nobody
Status: ASSIGNED → NEW
Comment 10•9 years ago
|
||
Mass update: Resolve wontfix all issues with legacy homescreens.
As of 2.6 we have a new homescreen and having these issues open is confusing. All issues will block bug 1231115 so we can use that to re-visit any of these if needed.
You need to log in
before you can comment on or make changes to this bug.
Description
•