Closed
Bug 247301
Opened 20 years ago
Closed 19 years ago
mous cursor set to wait status after universal scroll from logitech mouse is disabled
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: ramach, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040614 Firefox/0.9 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040614 Firefox/0.9 I press the mouswheel to activate the universal scroll functionallity of the logitech mouse. scroll a bit around a page and the press the mousewheel again to exit the universal scroll state, now th mouse cursor is set to the wait status. This problem exists only if you have the mouse driver of logitech installed it does not occur if you have the windows standard mouse driver with a logitech mouse. This is quite anoying since you are not sure if the browser is still working or if it is this bug. if you move the mouse after the exit the state is set back to default. Reproducible: Always Steps to Reproduce: 1.click mousewheel to enable Logitech univeral scroll 2.click mousewheel to disable Logitech universal scroll Actual Results: 1.mouse cursor is in wait staus 2.move mouse and cursor is set back to default status Expected Results: mouse cursor is set back to default status imediatly after the universal scroll is disabled.
Reporter | ||
Comment 1•20 years ago
|
||
this occured with mouse ware 9.42. universal scroll is not working at all with the actual mouse ware 9.79 see bug 183839 for details.
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 2•19 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 3•19 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: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•