1202251 - Tiles on New Tab page can't be moved to another line if you have to scroll to that line

Status: RESOLVED WONTFIX

(Firefox :: New Tab Page, defect)

Description

[arni2033]

Attachment: video - Tiles on New Tab page can't be moved to another line if you have to scroll to that line.webm

STR:   (Win7_64, Nightly 43, 32bit, ID 20150901030226, new profile, safe mode)
1. Open new tab page
2. Make sure you have enough tiles to cause overflow on New Tab
3. Make sure you have invisible row of tiles
4. Try to move a tile to an invisible row of tiles

Result:       Currently there's no way to do that
Expectations: There should be a way to do that: either smooth scrolling (like during drag and drop selected text) or just scrolling by Mouse wheel

Comment 1

[maxim zhilyaev]

This appears as expected behavior.  The tile rows have to be visible in order to move and drop into it.

Comment 2

[arni2033]

Yes. I filed this bug, because this also will be the first feedback once the feature reaches Release.
Reference of suggested behavior: drag and drop operations in History/Bookmarks/Library.

The current mock-up does not seem well thought out. Ofc, if you think it's OK, close this as Wontfix.

Comment 3

[maxim zhilyaev]

arni, good point. I mentioned in https://bugzilla.mozilla.org/show_bug.cgi?id=1202253#c5 that we will have to slow down on fixing non-critical bugs in FX because newtab is being re-architected. But, please, do file problems you noticed.

Comment 4

[arni2033]

(In reply to maxim zhilyaev from comment #3)
> newtab is being re-architected. But, please, do file problems you noticed.
Yes, I recieved that mail. I guess I'm okay with any resolution of a New Tab bug which is different from "closed, because it's not reproducible using your STR", because JS bugs must be reproducible

Comment 5

[Jessilyn Davis]

Hello!

This bug has been closed due to inactivity and/or the potential for this bug to no longer be an issue with the new Discovery Stream-powered New Tab experience.

Please help us triage by reopening if this issue still persists and should be addressed.

Thanks!