#3055 closed bug (wontfix)

Opened July 02, 2008 07:17AM UTC

Closed July 03, 2008 08:34PM UTC

Last modified July 16, 2008 01:10AM UTC

hovering elements over other elements while sorting

Reported by:	15steps	Owned by:	paul
Priority:	minor	Milestone:
Component:	ui.sortable	Version:	1.5.1
Keywords:		Cc:
Blocked by:		Blocking:

Description

While sorting, you can hover one element over another without the bottom element snapping out of the way. This demo is an example:

http://ui.jquery.com/repository/real-world/layout

Being able to hover one element over another isn't the default behavior for similar sortable interfaces. In other sortable interfaces, moving an element into another's space almost immediately moves the other element out of the way, i.e. you can't as easily hover one tile over the other. For examples of other sortable interfaces:

http://www.google.com/ig

http://www.netvibes.com/

http://interface.eyecon.ro/demos/sort.html

Attachments (0)

Change History (5)

Changed July 03, 2008 08:34PM UTC by paul comment:1

resolution:	→ wontfix
status:	new → closed

This is not a bug, but a thoughful implementation. However, we've added other tolerance modes for it - For example, tolerance: "pointer."

Changed July 08, 2008 03:16AM UTC by 15steps comment:2

Thanks for the response and advice on how to fix the default so it acts more like other sortable interfaces.

To correct, the option is documented as "distance" not "tolerance."

Changed July 08, 2008 04:41AM UTC by 15steps comment:3

Replying to [comment:1 paul]:

This is not a bug, but a thoughful implementation. However, we've added other tolerance modes for it - For example, tolerance: "pointer."

I was wrong: setting "distance" to 1 doesn't enable the desired behavior and I don't see "tolerance" as a documented option for sortables (it is documented for draggables). Though not documented, "tolerance: pointer" doesn't enable the desired behavior either. Is there some other option that might be enabled to stop elements from hiding one another?

What reasons are there for allowing sorted elements to hide one another? I'm curious to know why the development team would depart from what seems like standard behavior. If this isn't the place to ask for development rationale, apologies in advance.

Changed July 09, 2008 05:38PM UTC by paul comment:4

I think I don't really understand what you mean by hiding another element...could you maybe post it to the mailing lists? Thanks!

Changed July 16, 2008 01:10AM UTC by 15steps comment:5

Replying to [comment:4 paul]: