Closed Bug 380252 Opened 18 years ago Closed 16 years ago

Clicking back and forward buttons on MX1000 echos text characters in text fields

Categories

(Firefox :: General, defect)

2.0 Branch
x86
Windows XP
defect
Not set
minor

Tracking

()

RESOLVED DUPLICATE of bug 259450

People

(Reporter: jonlam, Unassigned)

References

Details

(Whiteboard: need logitech mice to confirm)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3 System Details: Microsoft Windows XP Pro w/SP2 Logitech MX1000 Mouse, Driver/SetPoint version 3.30.165 When I click back or forward buttons they echo the ♦/♠ (respectively) characters. As far as I can tell this does not happen in IE. Although a minor annoyance, it does affect searching for text on a page if you're flipping between pages because then you have to delete that char before finding the text again. Reproducible: Always Steps to Reproduce: 1. Install Logitech SetPoint 3.30.165 and use MX1000 2. In webpage select a text field either in webpage or in the browser (like the search box) 3. Click the back/forward buttons. A text char (♦ or ♠)will appear. Actual Results: If you're doing on the only page in the back/forward history (i.e. they're greyed out) you get the apperance that you're typing in that char. If you're doing it while the text cursor is in the URL/search text/search engine text fields, the char will appear while click back/forward. Expected Results: Those characters should not be echoed.
Version: unspecified → 2.0 Branch
Whiteboard: need logitech mice to confirm
can confirm behaviour with Logitech MX 620 System Details: Microsoft Windows XP Home SP2 Logitech SetPoint 4.40.88
appears in other Applications too, even in some standard windows dialogs -> seems to be a SetPoint problem
duplicate of Bug 259450 (see Workaround there)
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.