501885 - Attempting to perform a drag operation in the Rico (http://openrico.org/) "Simple" drag & drop demo results in a JavaScript error

Status: RESOLVED INVALID

(Core :: DOM: Copy & Paste and Drag & Drop, defect)

Description

[Randy Erb]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5

Attempting to perform a drag operation in the Rico "Simple"
drag & drop demo results in the following JavaScript error:

Error: draggable.isSelected is not a function
Source File: http://demos.openrico.org/javascripts/ricoDragDrop.js?1179206506
Line: 84

The url for this demo is http://demos.openrico.org/demos/drag_and_drop_simple

This error prevents any drag and drop operations.  It does not occur with previous versions of FireFox.

Reproducible: Always

Steps to Reproduce:
1.  Load the Rico "Simple" drag & drop demo page at http://demos.openrico.org/demos/drag_and_drop_simple
2.  Attempt to drag the draggable object
3.  It will fail and produce a JavaScript error

Comment 1

[Ria Klaassen (not reading all bugmail)]

Confirmed on Windows XP. Regression range is: http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2008-08-27+03%3A00%3A00&enddate=2008-08-27+07%3A00%3A00
Could be caused by Bug 356295.

Comment 2

[Neil Deakin]

You need to upgrade to a newer version of the rico library where this is fixed. See also bug 488976.

Comment 4

[Bill Gerba]

So you're seriously telling the 1,000s of sites that use the older version of
the rico library to upgrade in order to be compatible with the browser? That
seems rather backward.

Comment 5

[Neil Deakin]

(In reply to comment #4)
> So you're seriously telling the 1,000s of sites that use the older version of
> the rico library to upgrade in order to be compatible with the browser? That
> seems rather backward.

What would you suggest instead?

The rico code was setting a draggable property on elements, which now exists as a boolean property (as per the drag and drop specification), to a value that wasn't a boolean and an error was occuring.

Comment 6

[ralp.no.h]

Well hey, maybe FireFox 3.6 will adopt a standard that defines the href property on <a> elements as a boolean.  Then the fix is just to update all the existing markup, right?