#5003 closed bug (fixed)
Scroll on Droppable Demo Breaks Demo
Reported by: | HershelSR | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 1.8.14 |
Component: | ui.droppable | Version: | 1.7.2 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
To recreate:
- Go to http://jqueryui.com/demos/droppable/
- Drag the draggable box below the containing box to trigger a vertical scroll bar
- Return the draggable box up to the target and release
- Nothing happens
- Move the box another tiny bit and now it works
Movie attached of bug for clarify
Attachments (1)
Change History (7)
Changed 13 years ago by
comment:1 Changed 13 years ago by
comment:2 Changed 13 years ago by
Milestone: | TBD → 1.8 |
---|---|
Priority: | minor → major |
comment:3 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Droppable: Added dragStart and dragStop to ddmanager and call them from draggable to recalculate droppable positions after a drag causes a scroll. Fixes #5003 - Scroll on Droppable Demo Breaks Demo
Changeset: 67bd872fe1f8c4763d646f4eca852777e6f7a126
comment:4 Changed 12 years ago by
Merge pull request #352 from kborchers/bug_5003_3
Droppable: Added dragStart and dragStop to ddmanager and call them from draggable to recalculate droppable positions after a drag causes a scroll. Fixes #5003 - Scroll on Droppable Demo Breaks Demo
Changeset: 12f73d623e54a37cc347f48db4c7dea23648ba1e
comment:5 Changed 12 years ago by
Droppable: Added dragStart and dragStop to ddmanager and call them from draggable to recalculate droppable positions after a drag causes a scroll. Fixes #5003 - Scroll on Droppable Demo Breaks Demo (cherry picked from commit 67bd872fe1f8c4763d646f4eca852777e6f7a126)
Changeset: ce2fbb9429dd5fcaf80b1f3eef3d922b7ca06ec8
comment:6 Changed 12 years ago by
Milestone: | 1.9 → 1.8.14 |
---|
The option refreshPositions helps:
$('#draggable').draggable('option', 'refreshPositions', true);
Anyway it should be considered to take this example as a use case for the option refreshPositions.
The part of the current documentation ”… This solves issues on highly dynamic pages …“ is not very specific.