Closed Bug 1033510 Opened 10 years ago Closed 10 years ago

Dragging an icon to a smart collection can cause reordering

Categories

(Firefox OS Graveyard :: Gaia::Everything.me, defect)

All
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v2.0 affected, b2g-v2.1 affected)

RESOLVED WONTFIX
Tracking Status
b2g-v2.0 --- affected
b2g-v2.1 --- affected

People

(Reporter: cwiiis, Unassigned)

References

()

Details

(Whiteboard: [2.0-VH-bug-bash][systemsfe])

When dragging an icon to a smart collection, if you let it settle in a position before hovering over the collection, after dropping it in that collection it will reappear in the position you let it temporarily settle in, instead of where you originally dragged it from.
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking-]
Whiteboard: [2.0-VH-bug-bash][systemsfe]
Component: Gaia::Homescreen → Gaia::Everything.me
I think we need a video here before we triage this.
Blocks: 1015336
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking-] → [VH-FL-blocking-][VH-FC-blocking?]
Keywords: qawanted
Hmm, changing this behavior seems like it might have big implications for drag drop code? Isn't this basically what happens outside of collections? When the user idles in one spot long enough, we create an empty space for the icon, and that's the new home for the icon.
QA Contact: ckreinbring
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking?] → [VH-FL-blocking-][VH-FC-blocking?][QAnalyst-Triage?]
Video clip is now available.
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking?][QAnalyst-Triage?] → [VH-FL-blocking-][VH-FC-blocking?][QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
UX - The actual behavior here is a bug, right? If so, do you think it's a blocker from your perspective?
Flags: needinfo?(firefoxos-ux-bugzilla)
I don't really think it's a bug, if we returned the icon to it's original position, all of the icons would shift again as you drag the icon into the smart collection. I think this is potentially a lot more jarring than the current state. Curious as to what UX says though.
Flagging Francis.
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(fdjabri)
And not a blocker, don't think.
Alright, that aligns with what I was thinking. If Francis ends up disagreeing, then let me know & we'll reevaluate.
Blocks: vertical-home-next
No longer blocks: 1015336
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking?][QAnalyst-Triage+] → [VH-FL-blocking-][VH-FC-blocking-][QAnalyst-Triage+]
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking-][QAnalyst-Triage+] → [VH-FL-blocking-][VH-FC-blocking-][QAnalyst-Triage+][lead-review+]
Seems like the right behavior to me - and so not a bug - but flagging Jacqueline as this is her realm.
Flags: needinfo?(fdjabri) → needinfo?(jsavory)
I agree with Francis, I think this behaviour works well and we should keep it. I would vote that this is not a bug.
Flags: needinfo?(jsavory)
Ok, let's keep this for now, and if we find improvements to UX interactions in the future we can certainly revisit.
No longer blocks: vertical-home-next
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.