Bookmark mgr scrolls improperly



15 years ago
13 years ago


(Reporter: q1, Assigned: p_ch)


Mac OS X

Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040616 MultiZilla/
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040616 MultiZilla/

Upward scrolling doesn't work properly in the bookmark manager.

When scrolling by clicking the up-arrow, only the top line changes.

When scrolling by dragging the scroll box, only the top few lines change, and
video garbage often appears.

When scrolling by using my touchpad's upscroll capabilities, only the top few
lines change and video garbage often appears.

Scrolling by clicking in the areas between the scroll box and the top or bottom
of the scroll bar works properly.

Reproducible: Always
Steps to Reproduce:
See "details"
Actual Results:  
See "details"

Expected Results:  
See "details"
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.