Skip to main content

Search and Top Navigation

#3979 closed bug (fixed)

Opened January 29, 2009 12:43PM UTC

Closed January 31, 2009 04:54PM UTC

Last modified January 17, 2010 06:11AM UTC

Sortable connectWith fails

Reported by: Marc Diethelm Owned by: scottgonzalez
Priority: blocker Milestone: 1.7
Component: ui.sortable Version: 1.6rc6
Keywords: sortable, connectWith Cc: boo@chic-happens.ch
Blocked by: Blocking:
Description

Connecting one sortable to another fails with following error (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.5) Gecko/2008121622 Ubuntu/8.10 (intrepid) Firefox/3.0.5):

[Exception... "'Syntax error, unrecognized expression: #' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)" location: "<unknown>" data: no]

Tested with latest (trunk).

attaching testcase

Attachments (1)
Change History (7)

Changed January 31, 2009 02:27AM UTC by rdworth comment:1

milestone: TBD1.6
priority: criticalblocker
version: → 1.6rc6

Changed January 31, 2009 04:43PM UTC by scottgonzalez comment:2

owner: → scott.gonzalez
status: newassigned

Changed January 31, 2009 04:54PM UTC by scottgonzalez comment:3

resolution: → fixed
status: assignedclosed

Fixed in r1936.

Changed January 31, 2009 08:06PM UTC by Marc Diethelm comment:4

I'm sad to report I'm still seing an error here:

[Exception... "'Syntax error, unrecognized expression: #' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)" location: "<unknown>" data: no]

Changed February 12, 2009 10:55AM UTC by Marc Diethelm comment:5

In Fx 3.1b2 the error is different:

"uncaught exception: Syntax error, unrecognized expression: #"

Changed February 12, 2009 11:45AM UTC by Marc Diethelm comment:6

Ok, when the connectWith selector is wrapped in an array the error disappears. This effectively fixes the problem but really needs to be documented.

Changed February 13, 2009 04:43AM UTC by scottgonzalez comment:7

This is fixed. I'm not sure how view.jquery.com gets updated, but these files are not current. You should test against http://jquery-ui.googlecode.com/svn/trunk.