Skip to content
This repository has been archived by the owner on Dec 8, 2017. It is now read-only.

iOS: Drag with drag sensitivity > 0 starts at wrong location #171

Open
GoogleCodeExporter opened this issue Mar 13, 2015 · 2 comments
Open

Comments

@GoogleCodeExporter
Copy link

Does the issue occur in "quirks mode", "standards mode" or both? If you
don't know, does your HTML page contains a DOCTYPE declaration?
N/A

What version of GWT are you using? 1.4.60? 2.0.4? Other?
 * 2.5.0

What version of the gwt-dnd jar file or library file are you using?
 * 3.2.3

What operating system(s) are you using? Windows? Linux? Mac?
 * Issue only applies to iPad (iOS). Can be demonstrated on iPad simulator.

Does the issue occur in web mode, development mode (formerly "hosted
mode"), both or don't know?
 * Web mode (development mode not available for iPad)

What browser(s) do you use? Chrome, Firefox, IE, Safari, other?
 * Mobile Safari. Also includes iOS app embedded browser (UIWebView), which is nearly (but not completely) identical to Safari.
What is the browser version (if you know) from Help->About?
 * Information not available for Mobile Safari. However, iOS version includes 6.1 and 5.1.

What steps will reproduce the problem? Please attach sample code if you
can.
 * Reproducible using your demo (http://allen-sauer.com/com.allen_sauer.gwt.dnd.demo.DragDropDemo/DragDropDemo.html#BinExample). 

1. Set Drag Sensitivity to non-zero.
2. Press and hold on widget.
3. Move to just the sensitivity amount.

What is the expected output? What do you see instead?

Expected: Drag starts at current widget location.
Observed: Drag starts substantially offset, possibly outside of constrained 
boundary. (With the demo, if the widget is released, it will be misplaced).


Do you have a workaround?
* No workaround possible.

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 14 May 2013 at 8:04

@GoogleCodeExporter
Copy link
Author

Additional comment: It appears that removing the following code (lines 404-405 
of MouseDragHandler) fixes the issue. Unclear what other side effects may be, 
however.

          x += location.getLeft();
          y += location.getTop();

Original comment by [email protected] on 14 May 2013 at 9:05

@GoogleCodeExporter
Copy link
Author

Patch that makes these changes attached.

Original comment by [email protected] on 27 Jun 2013 at 3:36

Attachments:

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant