Search and Top Navigation
#8810 closed bug (duplicate)
Opened November 12, 2012 11:25PM UTC
Closed November 13, 2012 01:18PM UTC
Sortable Position Not Calculating Correctly
| Reported by: | arpowers | Owned by: | arpowers |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.10.0 |
| Component: | ui.sortable | Version: | 1.9.1 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
I appears that an attempt was made to make sortables calculate their position better.
This commit:
Unfortunately, it appears that this new calc system does not work at all for large draggables. Often the calculated 'drop spot' is off screen and this commit renders the plugin useless.
I recommend a reversion to the previous code until an option or more versatile system can be implemented.
A couple 20 second vids to further explain:
This is how its supposed to work:
http://screencast.com/t/ZPHr5MW5YQ
This is how it works with the new methodology (it doesn't!)
Attachments (0)
Change History (5)
Changed November 13, 2012 12:07AM UTC by comment:1
Changed November 13, 2012 01:45AM UTC by comment:2
| owner: | → arpowers |
|---|---|
| status: | new → pending |
@arpowers You can use http://jsfiddle.net/ZgAqH/ to get started. Open the link and click to "Fork" (in the top menu) to get started.
Note also that #8792 was reported as a regression caused by the referenced commit.
Changed November 13, 2012 04:40AM UTC by comment:3
| _comment0: | Alright, took me a minute but I got it duped. \ \ Here is the JS fiddle: \ http://jsfiddle.net/a7rxv/ \ \ Seems similar to the problem mentioned in the regression. → 1352782245833195 |
|---|---|
| status: | pending → new |
Alright, took me a minute but I got it duped.
Here is the JS fiddle:
http://jsfiddle.net/arpowers/a7rxv/1/
Seems similar to the problem mentioned in the regression.
Changed November 13, 2012 04:41AM UTC by comment:4
I can verify that it is the nested elements that are also floated ...
Thanks! Can you please provide a fiddle as well!