Closed Bug 702899 Opened 13 years ago Closed 7 years ago

mouse scroll wheel click sent to plugin as button number 0

Categories

(Core Graveyard :: Plug-ins, defect)

8 Branch
x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: duncantebbs, Assigned: smichaud)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20100101 Firefox/8.0
Build ID: 20111104165243

Steps to reproduce:

Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20100101 Firefox/8.0

We have an NPAPI plugin that uses the Cocoa event model on OSX, receiving events from the browser to handle user input.


Actual results:

When the user clicks the mouse wheel down (clicking, not scrolling), other browsers send a mouse down event with button number 2, whereas firefox sets the button number to 0 (making the event indistinguishable from a left mouse click).
Does this happen with FF 7.0.1?

Does it happen with recent mozilla-central (trunk) nightlies?

Are you able to test on other platforms (like Windows or Linux)?
(Following up comment #1)

Never mind.  I've answered all my questions (and confirmed this bug)
using my Debug Events Plugin from bug 441880.  I tested	on OS X	10.7.2
with a Mighty Mouse.  I've no reason to	think this bug won't also
happen on OS X 10.6.8 and 10.5.8.

In Cocoa event mode, FF gets both the "button number" and the "click
count" wrong.  With an "other mouse" event (what you get when you
press "Button 3") the button number should be '2', and the click count
should be '1' on a "down" event and '0' on an "up" event. 

This goes back to FF 4.0 -- the first FF release that supported the
Cocoa event model.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee: nobody → smichaud
Resolving old bugs which are likely not relevant any more, since NPAPI plugins are deprecated.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.