Unable to scroll by mouse wheel and keyboard, scroll bar works

RESOLVED EXPIRED

Status

RESOLVED EXPIRED
15 years ago
10 years ago

People

(Reporter: marc, Unassigned)

Tracking

Trunk
x86
Linux

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a2) Gecko/20040615
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a2) Gecko/20040615

I recently noticed that Mozilla seomtimes refuses scrolling a page by mouse
wheel and keyboard, the scroll bars, however, work. But - in rare cases - not
even these work. I may click-and_drag the bars, but clicking the area with nor
bar actually in results in ... guess ... nothing. The same applies to
<textarea>/<select> scroll bars. <select> list may, however, by crawled by using
the keyboard's UP/DOWN/PGUP/PGDOWN keys. I cannot exactly tell what
circumstances are affecting the browser to do so, but I'll try to figure out.

I've the Tabbrowser Extensions installed. The behavior seems to only come up
when multiple tabs are opened at the same time (I guess around 8+) and the
system has undergone some heavy load. After the first tab is 'visibly locked' it
sometime seems the effect spreads over to other tabs as well.

The effect is not aware of the pages which are 'locked' having frames, DHTML or
whatever. It may happen anytime anywhere. But: ofter there are forms on the
pages that get 'locked'.

Reproducible: Didn't try
Steps to Reproduce:
1. Use Mozilla as usual
2. Open some tabs (6,7,8 ...)
3. Make your box have load (???)
4. Be unable to scroll some pages...

Actual Results:  
Simetimes 'visual locked' pages

Expected Results:  
Scroll ;)

I'll update to the current CVS later today to see if the problem persists. As
the recent checkins do not promise any change to the behavior. But, hey ... the
change went in with no 'hint' as well...

Happy hacking, folks. I would if I just could. ;)

Comment 1

15 years ago
Is could be bug 97283 that you are seeing.
(Reporter)

Comment 2

15 years ago
(In reply to comment #1)
> Is could be bug 97283 that you are seeing.

I don't think so. I does not only affect any <DIV> or whatever. It affects the
whole visible area as well as <TEXTAREA> (!) / <SELECT> (!) elements.

HTH,
Marc
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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.