New Drag and Drop JS API does not work with Jetpack installed




Drag and Drop
8 years ago
5 years ago


(Reporter: pascalc, Unassigned)



Firefox Tracking Flags

(Not tracked)




(1 attachment)

Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9.2b4) Gecko/20091124 Firefox/3.6b4

1/ install jetpack extension (I have version 0.6.2)
2/ go to
3/ drag and drop a jpeg image in the drop box area

expected result:
Area gets bigger on hover avec file dropping is detected with a thumnail created

actual result:
Page is replaced by the local File:// link to the image

Deactivate Jetpack in the add-ons manager avec the demo will work correctly
Flags: blocking-firefox3.6?
Got this confirmed by somebody else on Linux. CC'ing Atul in case he has some insight.

FWIW, it's working for me with Jetpack installed on OSX & today's 3.6 nightly
Why do we think this is a Firefox blocker, and not a JetPack blocker?
The more I look at this bug, the more I think it's not a blocker until proven to be a problem with Firefox instead of JetPack; the only bit that trips me up is that it's Linux only.

Removing the blocking nomination until someone answers my question in comment 2, and adding Enn to see if the fact that this is a linux-only problem gives him pause, as well.

--> Core::Drag and Drop
Component: General → Drag and Drop
Flags: blocking-firefox3.6?
Product: Firefox → Core
QA Contact: general → drag-drop

Comment 4

8 years ago
I confirm that this is happening with me with JetPack installed (3.6 Beta 5).  I disable Jetpack, DnD works fine. (using Linux/Ubuntu)
For information, this bug is still there with Jetpack 0.7

Comment 6

8 years ago
yes it is there with 0.7

Comment 7

8 years ago
Sounds like it's from the slidebar.

The XBL slidebar.xml#stack is a stack (display: -moz-stack;) and for some reason doesn't forward dragenter event to the web content (if I remove -moz-stack, it works).
(In reply to comment #7)
> (if I remove -moz-stack, it works).

Does it affect the slidebar's functionality? (We're likely getting rid of it after 0.8 anyway, but if we can fix this bug in this release, we might as well.)
The stack is there to put content over slidebar contents to work around bug 130078. Pretty sure I needed the -moz-stack and crazy binding stuff to get things working, but if it's not necessary.. even better!

Comment 10

8 years ago
Yes, it affects the slidebar.

I'm trying to understand why the propagation of this event is stopped.

Comment 11

8 years ago
Created attachment 426244 [details]
extension testcase

The webpage doesn't receive the event because the slidebar (a <browser/>) is behind the tabbrowser (<browser type="content"/>).

A simple test case to reproduce the bug outside of jetpack:

    <browser flex="1"/>
    <browser type="content" flex="1"/>

The content of the second browser doesn't receive the event and only if it's a type="content" (or content-primary).

Testcase attached.
Install extension, then open test.xul:


Drag'n Drop a file into the web page: no visual feedback (the dropzone should be bigger). Toggle the stack: visual feedback (event received).
You need to log in before you can comment on or make changes to this bug.