Opened 11 years ago
Closed 9 years ago
#13304 closed defect (patchwelcome)
FloatingPane problem with mouse moving (out of window) in FF
Reported by: | nicola.besagni | Owned by: | dylan |
---|---|---|---|
Priority: | high | Milestone: | 1.9 |
Component: | DojoX Layout | Version: | 1.6.1 |
Keywords: | FloatingPane | Cc: | |
Blocked By: | Blocking: |
Description
I create a floating pane, show it. Then I move it via mouse. In FF5 if I try to move floating pane outside the browser window, I succeed. For right and bottom margin, floating pane is recoverable via scroll bar, but for top and left margin this is not possible.
This not happen in IE8
Attachments (1)
Change History (5)
Changed 11 years ago by
comment:1 Changed 11 years ago by
Component: | Dojox → DojoX Layout |
---|---|
Owner: | changed from Adam Peller to dante |
comment:2 Changed 9 years ago by
Milestone: | tbd → 1.9 |
---|---|
Owner: | changed from dante to dylan |
Status: | new → assigned |
Summary: | FloatingPane problem with mouse moving (out of window) in FF5 → FloatingPane problem with mouse moving (out of window) in FF |
Still an issue in Firefox 19.
comment:3 Changed 9 years ago by
I investigated this issue using the provided test page and FF 19.
This ticket assumes that the behavior in IE8 is the "correct" behavior, and that FF5 (and FF19, as well as Chrome, Safari, and Opera latest) are behaving wrongly. When a FloatingPane? is active and being dragged offscreen, all modern browsers allow this action to occur - e.g. DOM events continue even after the cursor has exited the boundaries of the browser window, assuming (in this case) that the mouse button is still held down and the FloatingPane? remains active. With oldIE, however, these events are killed immediately when the cursor leaves the boundaries of the browser window regardless of whether the dragged Pane is still active.
After digging through the repos, I couldn't find any code (past or present) that ever explicitly overrode oldIE functionality as far as FloatingPane? movement extending past window boundaries, and I'm not sure that's something worth putting time into at this point.
@dylan, what do you think?
comment:4 Changed 9 years ago by
Resolution: | → patchwelcome |
---|---|
Status: | assigned → closed |
I guess we can assume that IE8 is actually wrong here, even though it might be more desirable behavior, so will close as wontfix. A patch will be welcome to change this, but it's not simple.
using dojo-release-1.6.1