#6350 closed defect (wontfix)
Problems with dnd from a source in one ContentPane to a target in another ContentPane.
Reported by: | guest | Owned by: | bill |
---|---|---|---|
Priority: | high | Milestone: | 1.2 |
Component: | Dijit | Version: | 1.0 |
Keywords: | dnd ContentPane | Cc: | Eugene Lazutkin |
Blocked By: | Blocking: |
Description
I've tried a number of different versions of this but any time my source and target are in different ContentPanes? dnd stops working. I first encountered this using Dojo 1.0.x off the CDN. I've also tried it with a downloaded copy and most recently a copy checked out from trunk this morning. My browser is 2.0.0.13 on Ubuntu.
I have two examples. My current example is attached but I have another example posted in the forms linked below.
You can contact me at grossk at charter dot com if I can be of any further assistance.
Attachments (2)
Change History (7)
Changed 13 years ago by
Attachment: | test2.html added |
---|
comment:1 Changed 13 years ago by
Component: | DnD → Dijit |
---|---|
Owner: | changed from Eugene Lazutkin to bill |
It seems like a content pane-related problem. By any chance does the content pane uses iframes?
comment:2 Changed 13 years ago by
Cc: | Eugene Lazutkin added |
---|---|
Milestone: | → 1.2 |
ContentPane doesn't use iframes.
This is a FF2 only (browser bug) when overflow: auto is specified on the source div, like ContentPane does. (I reproduced on FF2 windows.) You can only drop if you move your mouse out of the browser window itself. See also #5285 for the mention of overflow: auto... so you could consider this a DnD bug or a ContentPane bug depending on your point of view.
I'm attaching a simpler test case that doesn't use ContentPane, but also I'll see if I can update dijit.css so this problem doesn't occur.
Changed 13 years ago by
test case not using ContentPane?, showing problem w/overflow: auto on FF2
comment:3 Changed 13 years ago by
No, this bug is related to #4854, which I closed as "wontfix" after investing a considerable time in it. :-( It is a FF2 bug, and there is no workaround. It is triggered by "overflow: auto" in some configurations, and it looks like the content pane provides such configuration.
I don't know if it is possible to change the content pane code to avoid using "overflow: auto". If it is not possible, I suggest to close the bug with "wontfix" --- nothing we can do about it.
comment:4 Changed 13 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
OK, closing as wontfix (although basically this is a dup of #4854, or at least a manifestation of it).
The code at issue is in dijit.css:
.dijitContentPane { display: block; overflow: auto; /* if we don't have this (or overflow:hidden), then Widget.resizeTo() doesn't make sense for ContentPane */ }
Removing the overflow:auto would solve the problem, but it's bad because it's (arguably) a backwards-compatibility break, and also because it will break things like BorderContainer (the center pane won't have a scrollbar even when it needs one). Although that could be fixed with a .dijitBorderContainer * { overflow: auto; }
type rule...
In some cases the user may be able to stick style="overflow: visible;"
or style="overflow: hidden"
on to their ContentPane to avoid this problem. Of course, that won't work if the user wants a scroll bar.
small HTML page example of the problem