Closed
Bug 200045
Opened 23 years ago
Closed 23 years ago
smoothScroll causes "Advance to next unread message" message after every screenful in preview pane
Categories
(Core :: Web Painting, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 198987
People
(Reporter: dcroal, Assigned: roc)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030329
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030329
When I scroll my mail in the preview pane using spacebar=pagedown I get an
"Advance to next unread message" box after every screenful. This should only
happen when I reach the end of the message. This behaviour went away when I
turned smoothScroll off.
Reproducible: Always
Steps to Reproduce:
1.Enable smoothScroll via user_pref("general.smoothScroll", true);
2.Problem
3.Disable smoothScroll via user_pref("general.smoothScroll", false);
4.Problem gone
Actual Results:
When I scroll my mail in the preview pane using spacebar=pagedown I get an
"Advance to next unread message" box after every screenful.
Expected Results:
This should only happen when I reach the end of the message.
Related to #174049 I think
Comment 1•23 years ago
|
||
I see this as well. Also, you can see a similar effect if you use the
mousewheel over the ports iframe on tinderbox (both the frame and the containing
windows scroll!) Are we not cancelling an event across frames?
Comment 2•23 years ago
|
||
-> browser
Component: Mail Window Front End → Layout: View Rendering
Product: MailNews → Browser
Comment 3•23 years ago
|
||
-> roc
Assignee: sspitzer → roc+moz
Status: UNCONFIRMED → NEW
Ever confirmed: true
| Reporter | ||
Comment 4•23 years ago
|
||
It happens when the message is opened in it's own window too, not just in the
preview pane
The iframe problem from comment 1 is bug 199024
*** This bug has been marked as a duplicate of 198987 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•8 years ago
|
Component: Layout: View Rendering → Layout: Web Painting
You need to log in
before you can comment on or make changes to this bug.
Description
•