Closed
Bug 252351
Opened 21 years ago
Closed 20 years ago
scrolling freezes, no context menu, & no searching on tab
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: gavin353, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
I had scrolled mostly down the page, I "may" have gone to another tab and
returned (something I do quite often, without problems), then I found some
problems. All these problems relate to the one tab. No apparent problems with
other tabs in the same browser instance.
Problems:
(1) can't scroll up or down (neither by mouse wheel, nor by dragging scrollbar,
nor by clicking in the gully before or after the slider)
(2) Right clicking mouse does not bring up a menue.
(3) Typing letters does not initiate incremental search
All these actions I can successfully do in another tab (this one, that I'm
typing up the bug) of the same browser instance.
I have no problems deleting tabs and bringing up new tabs & content. The
original frozen tab is still unresponsive.
Pocessor utilisation is "normal", i.e. almost non-existent until I do
something... - regardless of being on the errent tab or another.
Reproducible: Didn't try
Steps to Reproduce:
1. go to URL
2. scroll down
3. ???
Actual Results:
see above
Expected Results:
scrolling and other actions should work as normal
I will delete this browser instance and retry the URL.
| Reporter | ||
Comment 1•21 years ago
|
||
Hmm...
The URL was the one displayed in the tab, but it does not relate to the page
that was displayed. :-(
If I can find the page I will post a another comment.
Summary: scrolling freezes, no context menu, & no searching on tab → scrolling freezes, no context menu, & no searching on tab
Comment 2•21 years ago
|
||
I believe I have experiernced the same bug on Mac OS X.
I am using the suite nightly (2004080808) on MacOS X 10.3.5
Here is my test case which causes this bug to appear:
1. Open a page with enough content to require scrollbars.
2. Use the scroll bar to navigate up and down the page.
3. Eventually, usually right away, Mozilla will cease ro respond to mouse
clicks, right clicks no longer brings up the context menu and clicking on links
no longer opens a new page.
This bug occurs regardless of the manner in which the scrollbar is used, i.e.
draging the widget, clicking an arrow, or clicking in the scrollbar.
I believe this bug can be triggered in other ways,but I have not discovered a
test case other than using the scrollbar. This bug is limited to vertical
scrollbars; horizontal scrollbars work fine and do not trigger this bug.
Updated•21 years ago
|
Product: Browser → Seamonkey
Comment 3•20 years ago
|
||
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/
Comment 4•20 years ago
|
||
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
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•