Search and Top Navigation
#14684 closed bug (invalid)
Opened October 07, 2015 08:05PM UTC
Closed October 24, 2015 08:33AM UTC
Sortable: null reference when dragging to top of list
Reported by: | mwilson64 | Owned by: | mwilson64 |
---|---|---|---|
Priority: | minor | Milestone: | none |
Component: | ui.sortable | Version: | 1.11.4 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
We have a sortable list in which the first item cannot be moved (ui_state_disabled) and nothing can be moved above it. If an item is dragged above the first item, we get the
the following JavaScript error in the _clear function:
line 14744
Unable to get property 'removeChild' of undefined or null reference
The parentNode is null resulting in the error. Similar code appears at line 13963 in the cancel function, but it is checking to see if parentNode exists before
performing the removeChild.
Attachments (0)
Change History (4)
Changed October 07, 2015 08:47PM UTC by comment:1
owner: | → mwilson64 |
---|---|
status: | new → pending |
Changed October 09, 2015 02:56PM UTC by comment:2
status: | pending → new |
---|
I've tried creating a jsFiddle that will recreate the issue and have not be able to do so.
http://jsfiddle.net/nLzoymwu/2/
Any recommendations are appreciated.
Changed October 09, 2015 03:49PM UTC by comment:3
status: | new → pending |
---|
If you can't recreate it, I'm not sure how we can try to fix it. I also see that you're changing the internals of the widget, so that may be related. Until we have a valid reduced test case showing the problem, there's not much we can do.
Changed October 24, 2015 08:33AM UTC by comment:4
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!
Can you please provide a reduced test case showing the problem?