Closed
Bug 842318
Opened 12 years ago
Closed 12 years ago
[HOMESCREEN] If you try to swipe right from the last desktop in edit mode, icons stop vibrating
Categories
(Firefox OS Graveyard :: Gaia::Homescreen, defect)
Tracking
(blocking-b2g:-, b2g18+ fixed, b2g18-v1.0.0 wontfix, b2g18-v1.0.1 wontfix)
RESOLVED
FIXED
| blocking-b2g | - |
People
(Reporter: carlosmartinez, Assigned: crdlc)
References
Details
Attachments
(1 file)
|
188 bytes,
text/html
|
vingtetun
:
review+
lsblakk
:
approval-gaia-v1+
|
Details |
Tested in unagi with Gecko-0ecc076.Gaia-4164424.
STR:
1-Longtap an icon (e.g. HERE maps) to enter edit mode
2-Swipe right to the last desktop
3-Swipe again
Expected result --> You can´t go to the right and icons are still vibrating, because you´re still in edit mode
Actual result --> Icons stop vibrating
| Reporter | ||
Updated•12 years ago
|
blocking-b2g: shira? → tef?
| Assignee | ||
Updated•12 years ago
|
Assignee: nobody → crdlc
Status: NEW → ASSIGNED
| Assignee | ||
Comment 1•12 years ago
|
||
This patch applies when users try to swipe but the new and current pages are the same, I mean, there is not navigation to other page. Homescreen works fine when pages were translated because it listens for transitionend event but in edge cases e.g. swipe from rigth to left on the last page on the grid there is not movement so not transitionend. What happen? Missed vibrating edit mode and dead listeners
Attachment #715391 -
Flags: review?(21)
Comment 2•12 years ago
|
||
It is not unreasonable to expect a user to get back into edit mode by holding down an icon again. Not blocker.
blocking-b2g: tef? → -
| Assignee | ||
Comment 3•12 years ago
|
||
IMHO this bug is not related to that, as far as I understand, the STR are:
1) Go to last page in the grid
2) Enter in edit mode and then icons start jumping
3) Swipe from right to left, obviously, you stay in the last page but icons stop jumping
4) If you swipe from left to right you go to previous page and then icons start jumping again
Comment 4•12 years ago
|
||
(In reply to Lukas Blakk [:lsblakk] from comment #2)
> It is not unreasonable to expect a user to get back into edit mode by
> holding down an icon again. Not blocker.
As Cristian explained in previous comment, it is a different kind of problem, so renominating again...
blocking-b2g: - → tef?
Attachment #715391 -
Flags: review?(21) → review+
| Assignee | ||
Comment 5•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 6•12 years ago
|
||
Comment on attachment 715391 [details]
Patch v1
NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings.
[Approval Request Comment]
Bug caused by (feature/regressing bug #):
User impact if declined: bad experience, maybe users can think that they are not in edit mode
Testing completed: yes
Risk to taking this patch (and alternatives if risky): low risk
String or UUID changes made by this patch:
Attachment #715391 -
Flags: approval-gaia-v1?
Updated•12 years ago
|
blocking-b2g: tef? → -
status-b2g18:
--- → affected
status-b2g18-v1.0.0:
--- → wontfix
status-b2g18-v1.0.1:
--- → wontfix
Comment 7•12 years ago
|
||
Comment on attachment 715391 [details]
Patch v1
This is still not a blocker, unless it's impossible to edit or drag icons in the direction of a screen that *does* exist. We'll take the fix for this unfortunate glitch as a v1-train uplift.
Attachment #715391 -
Flags: approval-gaia-v1? → approval-gaia-v1+
Comment 8•12 years ago
|
||
v1-train@51b35c221ced188428ee78b07e3c022d20dd740f
Comment 9•12 years ago
|
||
The bug is fixed in V1.0.1
Comment 10•12 years ago
|
||
(In reply to rafael.marquez from comment #9)
> The bug is fixed in V1.0.1
Uhh...what? If the bug isn't working now, file a followup. We've already landed the patches here to warrant closing the bug.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 11•12 years ago
|
||
Rafa wants to say what this bug is reproducible on v1.0.1. Do you want to re-open this one or we should create a follow up? Thanks a lot
Updated•12 years ago
|
blocking-b2g: - → tef?
Comment 12•12 years ago
|
||
I do not know which is the correct procedure. I want that this bug not be reproduced in v1.0.1
| Assignee | ||
Comment 13•12 years ago
|
||
FYI it happens only in v1.0.1 branch. Maybe, this old patch would merge on v1.0.1 but I prefer doing a specific patch in order to avoid new bugs.
Comment 14•12 years ago
|
||
This should not block the realease, we will track it.
blocking-b2g: tef? → -
You need to log in
before you can comment on or make changes to this bug.
Description
•