Search and Top Navigation
#8781 closed bug (invalid)
Opened November 06, 2012 08:57PM UTC
Closed December 01, 2012 09:11AM UTC
Global box-sizing: border-box breaks drag-and-drop in IE8
| Reported by: | brandmitchell | Owned by: | brandmitchell |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.10.0 |
| Component: | ui.draggable | Version: | 1.8.17 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
My team has found a rather annoying bug with draggable. When using the global * declaration of box-sizing: border-box, the draggable component breaks in IE8. The issue seems to be related to the box-sizing on the main html or body tags of a page. When in use, the draggable area works within the region first loaded in the browser's viewport. If a user scrolls, attempting to bring a draggable object into the region outside the original viewport, the draggable component 'breaks' and causes a scroll event scroll the page to the top.
Attachments (0)
Change History (3)
Changed November 06, 2012 09:42PM UTC by comment:1
| owner: | → brandmitchell |
|---|---|
| status: | new → pending |
Changed November 16, 2012 11:27PM UTC by comment:2
Here's a fiddle that demonstrates its broken behavior, but I am not sure how that has to do with JQueryUI!?
Changed December 01, 2012 09:11AM UTC by comment:3
| 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!
Thanks for taking the time to contribute to the jQuery UI project! Please provide a complete reduced test case on jsFiddle to help us assess your ticket.
Additionally, be sure to test against the git version of both jQuery UI and jQuery to ensure the issue still exists. To get you started, use this boilerplate: http://jsfiddle.net/ZgAqH/Open the link and click to "Fork" (in the top menu) to get started.
I can definitely investigate this issue, but I'll need a test case showing the issue.