Closed Bug 488976 Opened 15 years ago Closed 15 years ago

Drag & Drop of objects in Astaro Security Gateway 7.401 doesn't work

Categories

(Tech Evangelism Graveyard :: English US, defect)

Product:
Tech Evangelism Graveyard
Component:
English US
Platform:
x86_64
Windows Vista
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: salassin, Unassigned)

References

(
URL
)

Details

(Keywords: regression) 

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b4pre) Gecko/20090417 Shiretoko/3.5b4pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b4pre) Gecko/20090417 Shiretoko/3.5b4pre

In Astaro Security Gateway 7.401 (software appliance), which has a web interface, you can define objects (networks, services) that you use a lot (eg Laptop, which contains the address and the network interface).
When you create rules or packet filters, you then drag your object onto the corresponding field (eg. Traffic Source: Any, Traffic Destination: External WAN, where Any and External are objects).
Dragging does not work in FX 3.1 Beta 3 & FX 3.5 Beta 4, it does in FX 3.0.8, as in IE 8.

Reproducible: Always

Steps to Reproduce:
1. Install Astaro Security Gateway (there is a free Virtual Appliance for VMware Player)
2. Go to the web interface, log in
3. Define a Network under Definitions->Networks (eg. Laptop, with ipaddress of laptop and internal network as interface)
4. Go to Network Security->Packet Filter (this is only one place where objects are used)
5. Create a rule, click on the folder icon next to Source, try to drag your newly created 'laptop' object onto the field (or any other object)
Actual Results:  
The dragging does not work, so: nothing.

Expected Results:  
When you click and drag an object, you see it attached to your mouse pointer until you drop it onto a field (like Source), then you see the object is put into that field.

When checking out the source of the Astaro Security Gateway (mind you, i'm no programmer, so i don't actually know a lot about this), i find that the page is using js, json and perl scripting.
I suppose this will not only be a problem in Astaro, but as i don't know how the code works, i can't possibly tell to what scripting problem this could be related.
Oh, yet something else, the bug is verified by other Astaro users:
http://www.astaro.org/astaro-beta-versions/asg-v7-400-beta/24049-drag-drop-firefox-3-1-a.html
Component: General → Drag and Drop
Product: Firefox → Core
QA Contact: general → drag-drop
Bug still present in

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b5pre) Gecko/20090430 Shiretoko/3.5b5pre
I just verified the same bug in:

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2a1pre) Gecko/20090501 Minefield/3.6a1pre
The forum link shows a couple having this issue in trunk and Shiretoko builds, so a little help for these guys would be nice. The reporter also has verified this problem does not exist on IE 7 and IE 8.
Little extra info, which i put in the Description, but maybe not clearly enough:
It worked in Firefox 3.0.8.

Other than that, i have an answer from one of the people of Astaro, claiming that they didn't change any code, so that in his opinion it's a Firefox issue:

http://www.astaro.org/astaro-gateway-products/general-discussion-feature-requests/25484-will-firefox-3-5-a.html#post109170
So this is a regression against Firefox 3.0.x, right? So we need the regression range when this bug has been started for the first time. Reporter, it would be very helpful if you could run tests against nightly builds of Firefox. All builds are available here: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/. Probably it would be helpful to check the official releases first (a1,a2,...,b2).

Further, can this page be minimized as testcase? Even saving it locally would be helpful when the issue can be seen when opening it again afterward. Thanks.
Keywords: regression, regressionwindow-wanted
Version: unspecified → 1.9.1 Branch
OK, as to the question by Henrik on IRC, what is shown in error console with strict js enabled:

Following error comes up when hovering over a draggable item:

Error: aDraggable.getMouseDownHTMLElement is not a function
Source File: https://192.168.2.1:4444/core/js/rico.js?t=1241557952
Line: 1302
Following Henrik's questions, i tested on following builds (with strict js enabled), both with and without javascript.options.jit.content enabled:

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1a1) Gecko/2008072310 Shiretoko/3.1a1

-> Bug NOT present

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1a2) Gecko/20080829082037 Shiretoko/3.1a2

-> Bug NOT present

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b1) Gecko/20081007 Firefox/3.1b1

-> Bug PRESENT

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b2) Gecko/20081125 Firefox/3.1b2

-> Bug PRESENT

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3

-> Bug PRESENT

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b4) Gecko/20090423 Firefox/3.5b4

-> Bug PRESENT

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b5pre) Gecko/20090430
Shiretoko/3.5b5pre

-> Bug PRESENT

If any other tests are needed, don't hesitate to ask me. 
If i'm not being complete enough, please tell me exactly what info is needed.
Thanks. Yeah, we have to narrow it down a bit more. Would be great to get the day when it started. You should check nightly builds between the following two dates: 20080829 and 20081007. All those builds can be found here: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2008/
OK, I will check it out this evening (that's in about 6 hours for me ;-) ).
Ok, tracked down the last working / first not working version:

Last version in which the bug is not present:

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1a2pre) Gecko/20080827031643 Minefield/3.1a2pre

First version in which the bug is present:

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1a2pre) Gecko/20080828034823 Minefield/3.1a2pre
Thanks SalaSSin. That's very helpful.

Checkins in this timeframe: http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2008-08-27+00%3A00%3A00&enddate=2008-08-28+03%3A00%3A00

Possible candidates:
Bug 439565, crash with drag image not in document
Bug 356295. Implement HTML5 drag-drop. r=smaug,neil,sr=roc

I highly suspect bug 356295. Neil, what do you think?

It would be really great to have a testcase for this regression. But as SalaSSin told me on IRC saving as webpage complete doesn't reproduce this behavior. Could the pages somehow be isolated from the server which runs inside this machine?
Blocks: 356295
URL: http://www.vmware.com/appliances/dire...
Keywords: regressionwindow-wanted → testcase-wanted
This is a bug in the rico js library. It's setting a 'draggable' property on elements, but html5 drag/drop defines one. This was fixed on January 27. See http://sourceforge.net/tracker/index.php?func=detail&aid=2354541&group_id=140375&atid=746298
Assignee: nobody → english-us
Component: Drag and Drop → English US
Product: Core → Tech Evangelism
QA Contact: drag-drop → english-us
Version: 1.9.1 Branch → unspecified
Thanks Neil for the information.

SalaSSin, can you get in contact with Astaro to inform them about this change? You can reference this bug report. Confirming for now.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Thanks for the info.

I will forward the info to Astaro.
If i understand it correctly, Astaro should update their version of this rico js library, right?
We decided against a rico update, but applied the patches that fixes the issue. Fix will be part of the upcoming 7.500.
Thanks for your feedback and great to see that it will be fixed on your side. 

SalaSSin, when you could test the new version when it will be available and report back. Then we can resolve this bug as invalid.
Ok, exactly what i was thinking :-)

Is it already included in the new beta, 7.450, which has been released this friday?
(In reply to comment #20)
> SalaSSin, when you could test the new version when it will be available and
> report back. Then we can resolve this bug as invalid.

Since this is TE and the vendor is fixing it, this bug should be RESOLVED FIXED when it's finished.
ok, the 7.500 beta (official version number 7.450) does *not* fix the problem using Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b4) Gecko/20090423 Firefox/3.5b4 (.NET CLR 3.5.30729)
Correct -- the fix will be available in the next BETA up2date or release.
Problem has been resolved with the new 7.460 version released today.

Using Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1) Gecko/20090615 Firefox/3.5 (.NET CLR 3.5.30729)
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
That's fantastic. Thanks to everybody who was involved!
Status: RESOLVED → VERIFIED
Keywords: testcase-wanted
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.