Hello,
I have an ASP.NET application that uses a frameset (header frame, left-menu frame, and then content frame). I've searched for frame related posts and have found a few talking about the fact other frames don't disable, how to render above the frameset, etc, but none for this issue.
The behavior is this:
* Open a RadWindow (in this case, a modal dialog) in the content frame
* Left-click and hold the title bar and start dragging around.
* While dragging, move your cursor to another frame in the frameset. You'll note that the window stays in the content frame (good)
* While still in the other frame, release the mouse button.
* Move the cursor back over the content frame. Once you do, the radwindow will snap to the cursor position, and follow the cursor - even though the mousebutton is not being held. To "release" you have to left- click on the window again.
This issue is frustrating for a client; what they would like to see is the window is "released" as soon as the mouse is released. I suspect the combination of a frameset and browser capabilities may make this impossible - perhaps the browser is still firing the ondrag... But I'd love to know if there's a workaround.
I have an ASP.NET application that uses a frameset (header frame, left-menu frame, and then content frame). I've searched for frame related posts and have found a few talking about the fact other frames don't disable, how to render above the frameset, etc, but none for this issue.
The behavior is this:
* Open a RadWindow (in this case, a modal dialog) in the content frame
* Left-click and hold the title bar and start dragging around.
* While dragging, move your cursor to another frame in the frameset. You'll note that the window stays in the content frame (good)
* While still in the other frame, release the mouse button.
* Move the cursor back over the content frame. Once you do, the radwindow will snap to the cursor position, and follow the cursor - even though the mousebutton is not being held. To "release" you have to left- click on the window again.
This issue is frustrating for a client; what they would like to see is the window is "released" as soon as the mouse is released. I suspect the combination of a frameset and browser capabilities may make this impossible - perhaps the browser is still firing the ondrag... But I'd love to know if there's a workaround.