Closed
Bug 223542
Opened 21 years ago
Closed 19 years ago
Weird scrolling using autoscroll over iframe / frame
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: ruffo, Assigned: tuukka.tolvanen)
References
()
Details
Attachments
(1 file, 1 obsolete file)
4.31 KB,
patch
|
mconnor
:
review+
asa
:
approval1.8b4+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 Firebird/0.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 Firebird/0.7 Rendering of the page is ok. But if you scroll to the bottom with the middle-click-pointer thing ( ^ ) ( V ) and then put the mouse pointer to the webring table, the browser scrolls up and down in a weird way Reproducible: Always Steps to Reproduce: 1. go to that page 2. go to the bottom 3. middle-click once 4. put the pointer to the web-ring table Actual Results: Scrolls up and down in with non-deterministic fashion Expected Results: Just be quiet. Default theme used
Confirming on linux Gecko/20031024 Firebird/0.7+
Severity: normal → minor
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Summary: Weird scrolling → Weird scrolling using autoscroll over iframe
Comment 2•21 years ago
|
||
This looks (after an initial look at the page in question) like the autoscroll is calculating it's position relative to the iframe's origin when over it. This I think explains all the scrolling that then ensures. :)
Comment 3•20 years ago
|
||
this bug is fixed when the autoscroll looks at what frame it is initially showed, and the scrolling should only occur relative to that frame. It is also when you have two frames vertically and you scroll in the top one, and move your mouse in the bottom one, the top one will go back up. The bug also exists in firefox 0.8 voted.
Comment 4•20 years ago
|
||
*** Bug 237755 has been marked as a duplicate of this bug. ***
Updated•20 years ago
|
Flags: blocking1.0?
Updated•20 years ago
|
Flags: blocking1.0? → blocking1.0-
Able to replicate on xp firefox 0.9.1 at page: http://optimoz.mozdev.org/piemenus/ Added vote.
Assignee | ||
Comment 6•20 years ago
|
||
*** Bug 253085 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 7•20 years ago
|
||
*** Bug 251903 has been marked as a duplicate of this bug. ***
Assignee | ||
Updated•20 years ago
|
No longer depends on: 237755
Summary: Weird scrolling using autoscroll over iframe → Weird scrolling using autoscroll over iframe / frame
Assignee | ||
Comment 8•20 years ago
|
||
this approach wfm on linux aviary with the testcase pages.
Assignee: firefox → t.bugz
Status: NEW → ASSIGNED
Assignee | ||
Updated•20 years ago
|
Attachment #161730 -
Flags: review?(firefox)
Comment 9•20 years ago
|
||
*** Bug 270739 has been marked as a duplicate of this bug. ***
Comment 10•19 years ago
|
||
asking for blocking-aviary1.1. A patch exists, and it's quite annoying issue.
Flags: blocking-aviary1.1?
Version: unspecified → Trunk
Comment 11•19 years ago
|
||
*** Bug 272094 has been marked as a duplicate of this bug. ***
Comment 12•19 years ago
|
||
Not sure, but in bugzilla, if I have 2 bugs open in tabs, after closing one, and/or hitting reply in the other; it will get the contents of the two mixed together. Not sure if that is this bug or not.
Comment 13•19 years ago
|
||
(In reply to comment #12) > Not sure, but in bugzilla, if I have 2 bugs open in tabs, after closing one, > and/or hitting reply in the other; it will get the contents of the two mixed > together. Not sure if that is this bug or not. This is not a Firefox issue. It's due to an issue with bugzilla and viewing multiple bugs at once.
Comment 14•19 years ago
|
||
*** Bug 296024 has been marked as a duplicate of this bug. ***
Comment 15•19 years ago
|
||
*** Bug 296024 has been marked as a duplicate of this bug. ***
Comment 16•19 years ago
|
||
Tuuka, maybe it is better to reassign to mconnor@steelgryphon.com?
Comment 17•19 years ago
|
||
*** Bug 290364 has been marked as a duplicate of this bug. ***
Comment 18•19 years ago
|
||
*** Bug 296244 has been marked as a duplicate of this bug. ***
Updated•19 years ago
|
Attachment #161730 -
Flags: review?(firefox) → review?(mconnor)
Comment 19•19 years ago
|
||
minusing, but if the patch works out, it'll be fixed rsn.
Flags: blocking-aviary1.1? → blocking-aviary1.1-
Assignee | ||
Comment 20•19 years ago
|
||
bitrot (bug 280584) update to patch1
Attachment #161730 -
Attachment is obsolete: true
Attachment #186474 -
Flags: review?(mconnor)
Updated•19 years ago
|
Attachment #161730 -
Flags: review?(mconnor)
Comment 21•19 years ago
|
||
(In reply to comment #20) > Created an attachment (id=186474) [edit] > patch1.1 > > bitrot (bug 280584) update to patch1 How exactly do we use this patch, I am new to this bug stuff :P
Assignee | ||
Comment 22•19 years ago
|
||
> How exactly do we use this patch, I am new to this bug stuff :P
apply the changes with 'patch' to a current source tree or the contents of one
of the jar files in a trunk nightly install. Or wait for the fix to be checked
in and a version with the fix to be released :)
Comment 23•19 years ago
|
||
Patch works great on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050619 Firefox/1.0+ (applied manually to toolkit.jar) Surely this should be severity: normal at least as most pages have ads, and most ads are in iframes, so this occurs extremely often and is disorienting etc. when it does happen.
Comment 24•19 years ago
|
||
Comment on attachment 186474 [details] [diff] [review] patch1.1 using screen coords is really bad, perf-wise, see discussion the bookmarks contextmenu bug
Attachment #186474 -
Flags: review?(mconnor) → review-
Comment 25•19 years ago
|
||
I think Mike meant these remarks: bug 296004, comment 21 and bug 242833, comment 14.
In this case I think using screen coordinates would be OK. You're only doing it once per mouse move, if I understand the code correctly. That should not be a problem.
Comment 27•19 years ago
|
||
Comment on attachment 186474 [details] [diff] [review] patch1.1 In the light of comment 26, asking for rereview.
Attachment #186474 -
Flags: review- → review?(mconnor)
Comment 28•19 years ago
|
||
Comment on attachment 186474 [details] [diff] [review] patch1.1 let's get this in for b4, early, and get some testing in.
Attachment #186474 -
Flags: review?(mconnor) → review+
Updated•19 years ago
|
Attachment #186474 -
Flags: approval-aviary1.1a2?
Updated•19 years ago
|
Attachment #186474 -
Flags: approval-aviary1.1a2? → approval1.8b4?
Updated•19 years ago
|
Attachment #186474 -
Flags: approval1.8b4? → approval1.8b4+
Assignee | ||
Comment 29•19 years ago
|
||
checked in, http://bonsai.mozilla.org/cvsquery.cgi?date=explicit&mindate=2005-07-17%2006:43&maxdate=2005-07-17%2006:43
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 30•19 years ago
|
||
I saw that in Deer Park Alpha 2, the nightly build on July 18 seems to fix the autoscroll problem. But additionally, it seems that if you start an autoscroll inside a text ad (like in a forum, since those text ads can be right in the middle) autoscroll will not function. The page simply will not scroll. Try going to http://www.dslreports.com/forum/remark,13599896~mode=flat~days=9999~start=20 and starting an autoscroll right in the middle of the text ad.
Comment 31•19 years ago
|
||
(In reply to comment #30) > I saw that in Deer Park Alpha 2, the nightly build on July 18 seems to fix the > autoscroll problem. But additionally, it seems that if you start an autoscroll > inside a text ad (like in a forum, since those text ads can be right in the > middle) autoscroll will not function. The page simply will not scroll. Try going > to http://www.dslreports.com/forum/remark,13599896~mode=flat~days=9999~start=20 > and starting an autoscroll right in the middle of the text ad. If you start autoscrolling inside an iframe, you will be bound by it.
Comment 32•19 years ago
|
||
altosaxman@gmail.com, that's bug 251903.
You need to log in
before you can comment on or make changes to this bug.
Description
•