Community
Participate
Working Groups
Easy to reproduce with the demo application. Just drag the workbench shell down until it's partly hidden. You can now scroll up/down with the mousewheel. Note that no scrollbars are visible and the SWT Display doesn't get resized (seen when you maximize/restore the shell).
Benny, can we close this bug? To me it seems that this was fixed with one of the qx maintenance releases. I can't reproduce it anymore or am I missing something?
Cannot reproduce it with mouse wheel / trackpoint but it's still possible to scroll the page with Down and Up keys. Tested with FF 3.0.3. In webkit-based browsers the page has at least a scrollbar.
Created attachment 146838 [details] Proposed patch
Fixed in CVS HEAD
The fix prevents Tree and List from scrolling with mouse wheel.
Created attachment 147428 [details] New patch The "mousewheel" event handling is removed. Currently there is no problem with mouse wheel scrolling in Firefox, IE and Webkit browsers.
Applied second patch to CVS HEAD
This is causes bug 290248. Reverted changes.
Created attachment 148893 [details] experimental: setting body.position to "absolute" Setting body.position to "absolute" blocks any scrolling of the document. I could not make out any side-effect of this solution. I have also no idea why Qooxdoo sets position to "" in ClientDocument.js.
Known side-effects of body.position = "absolute" in FF. - Text in textfields can not be selected. - Clicking in a textfield won't make the cursor visible. - Keyboard-control in multi-line textfields is buggy. Those effects are emmediately gone if body.position is deleted via firebug. Only Firefox (tested 2.0 and 3.0) is affected. Works fine in Opera, Safari, Chrome and IE.
Created attachment 148980 [details] Proposed solution This should disable scrolling in Firefox without any side-effects. Info: - The textfield-bugs appear only if body-style has "-moz-user-select:none" and any value for "position". - The "-moz-user-select"-attribute is set by the "selectable"-property of ClientDocument. The property can savely be set to true in FF, as all the widgets that could be selectable should have this property set to false themselves. For the way "-moz-user-select" works, that suffices. - IE however needs "selectable" to be false, so the property is only changed in FF-browsers. - The reasion behind this behavior is unkown, except that FF has a long and troubled history with similar problems: https://bugzilla.mozilla.org/show_bug.cgi?id=167801
Applied patch to CVS HEAD