Current implementation in widget/src/beos/nsWindow.cpp reports fixed point (100,100) for NS_MOUSE_SCROLL. It results in stupid bugs on pages with scrollable iframe, like stopping of scrolling main content when iframe gets visible. On some pages it is impossible at all to scroll main content. Fix seems simple - adding GetMouse() to get cursor position, but it leads to strange behaviour - if you reached bottom of page, scroll-up moves to top of page, instead moving up for scroll-step. So investigating
oops, no problem with scrol-up. was stupid side-effect of another change in code. Submitting fix soon
Assignee: beos → sergei_d
Created attachment 153224 [details] [diff] [review] patch. diff -up4 gets cursor coordinates and assigns those to even point. compare wheel behaviour before and after patch here: http://beos.spb.ru/mozilla/frametest/testmain.html before patch wheel scrolling scrolls rather iframe than main page. after patch wheel scroll object at which it's over.
Comment on attachment 153224 [details] [diff] [review] patch. diff -up4 need to remove XXX comment
Attachment #153224 - Attachment is obsolete: true
Comment on attachment 153227 [details] [diff] [review] patch asking for review
Attachment #153227 - Flags: review?(thesuckiestemail)
Comment on attachment 153227 [details] [diff] [review] patch firstname.lastname@example.org
Attachment #153227 - Flags: review?(thesuckiestemail) → review+
fixed. new revision: 1.82
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → FIXED
Checkin on AVIARY by db48x%yahoo.com "Check in several BeOS bugs that are already checked in on the trunk. All are r=twh (email@example.com) except the last which is r=Sergei Dolgov (firstname.lastname@example.org). a=carte blanche ([03:53:40] <email@example.com> We've been basically given a carte blanche for any change that involves the beos-only code)"
You need to log in before you can comment on or make changes to this bug.