#9208 closed feature (invalid)

Opened April 04, 2013 05:16PM UTC

Closed April 19, 2013 08:34AM UTC

Sortable-Widget - Deactivation (disable) after mouse-capturing

Reported by: sebastian-marinescu Owned by: sebastian-marinescu
Priority: minor Milestone: none
Component: ui.sortable Version: 1.9.0
Keywords: Cc:
Blocked by: Blocking:
Description

Hi jQquery-Community,

I'm working on a project where we use jQuery and some UI-Widgets.

I have following scenario:

  • A stage with objects
  • The stage is draggable (own script)
  • The stage should also be draggable, if the user clicks and drags (left/right) over one of the mentioned objects
  • The objects should only be (re-)sortable, if the user is doing a "pull-down-gesture" on them

So I need to handle the mouse-events on my own. The problem with ''sortable'' is, that after a mouse-down, the widget captures this and even though I "disable" it before the delay is over (because it's not an "pull-down-gesture"), it still starts the sort-mechanism.

I already tried to use the "cancel"-method of the sortable-widget, but this behaves odd and is not what I actually want.

The solution for me is to check for the "disable"-option in the "_mouseStart" & "_mouseDrag" methods of the widget. I also started a pull for this (my first one, that's why I'm here :] ) - https://github.com/jquery/jquery-ui/pull/930

So, is this a bug, a feature or do I totally misunderstand something?

Thanks in advance,

Sebastian

Attachments (0)
Change History (2)

Changed April 04, 2013 05:25PM UTC by scottgonzalez comment:1

owner: → sebastian-marinescu
status: new → pending

So you're dragging or sorting based on the direction of the movement? Why don't you have clearly identified handles for the separate actions?

Changed April 19, 2013 08:34AM UTC by trac-o-bot comment:2

resolution: → invalid
status: pending → closed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!