Skip to main content

Search and Top Navigation

#4742 closed bug (worksforme)

Opened August 03, 2009 05:11PM UTC

Closed October 24, 2012 10:29PM UTC

Webkit browsers (safari + chrome) can't do delayed draggable

Reported by: mrabjohn Owned by:
Priority: minor Milestone: 2.0.0
Component: ui.draggable Version: 1.7.2
Keywords: webkit delay draggable distance Cc:
Blocked by: Blocking:
Description

I have found that on both Chrome for Windows 2.0.172.39 and Safari for Windows 4.0.2 there are problems with the draggable UI interaction.

I see this error if I create a div, with an icon (img) in it, the image won't drag if I set the "distance" option of the draggable to a non-zero value.

It would appear from my tests, that Chrome is only able to correctly process a drag operation if the user selects text. To this end I have derived a workaround - effectively if I fill my icon space with a div that fully obscures the icon and fill this new div with text i.e. "AAAAAA" and so on - the drag works. If I make this entire div have opacity zero, then problem solved.

Even though I've found a workable solution, I would much prefer it if you guys could take a look at this, DIVs filled with filler characters is hardly the most elegant solution ever devised!

Attachments (0)
Change History (4)

Changed August 04, 2009 08:16AM UTC by mrabjohn comment:1

I have discovered that:

A) A single very large character can be used to fill the area resulting in less hack code.

B) Use of the "-webkit-user-select: none" style is required on all elements that may be displayed as selected, otherwise the browser selection is displayed. Even if this is used, you still need the text layer.

Changed November 17, 2009 09:44AM UTC by jzaefferer comment:2

milestone: TBD1.8

Changed October 11, 2012 02:49PM UTC by scottgonzalez comment:3

milestone: 1.9.02.0.0

Changed October 24, 2012 10:29PM UTC by mikesherov comment:4

resolution: → worksforme
status: newclosed

Thanks for taking the time to contribute to the jQuery UI project! I can no longer reproduce the issue using the latest jQuery and jQuery UI. http://jsfiddle.net/AY6HP/1/

If you can still reproduce it, please feel free to reopen the bug. Thanks!