- From: Gary Kacmarcik <notifications@github.com>
- Date: Tue, 30 Jun 2020 19:31:09 -0700
- To: w3c/uievents <uievents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/uievents/issues/265/652150467@github.com>
Here is the behavior that I see on Mac (tested with https://domeventviewer.com/mouse-event-viewer.html): When the `contextmenu` handler calls preventDefault: | Browser | Action | Events | Notes | | --- | --- | --- | --- | | Firefox | Click | `mousedown`, `mouseup`, `click` | | | Firefox | Ctrl+click | `mousedown`, `contextmenu`, `mouseup`, `auxclick` | | | Firefox | 2-finger trackpad click | `mousedown`, `contextmenu`, `mouseup`, `auxclick` | | | Safari | Click | `mousedown`, `mouseup`, `click` | | | Safari | Ctrl+click | `mousedown`, `contextmenu`, `mouseup`, `click` | `click` should be `auxclick` | | Safari | 2-finger trackpad click | `mousedown`, `contextmenu`, `mouseup` | No `auxclick` | | Chrome | Click | `mousedown`, `mouseup`, `click` | | | Chrome | Ctrl+click | `mousedown`, `contextmenu`, `mouseup` | No `auxclick` | | Chrome | 2-finger trackpad click | `mousedown`, `contextmenu`, `mouseup`, `auxclick` | | Overall, Firefox is the most consistent. Ctrl+click and 2-finger-click should act the same, but Chrome and Safari are not. Safari should send `auxclick` for non-primary mouse clicks. When the `contextmenu` handler does *not* call preventDefault: | Browser | Action | Events | Notes | | --- | --- | --- | --- | | Firefox | Click | `mousedown`, `mouseup`, `auxclick` | | | Firefox | Ctrl+click | `mousedown`, `contextmenu`, `mouseup`, `auxclick` + menu | | | Firefox | 2-finger trackpad click | `mousedown`, `contextmenu`, `mouseup`, `auxclick` + menu | | | Safari | Click | `mousedown`, `mouseup`, `click` | | | Safari | Ctrl+click | `mousedown`, `contextmenu` + menu | No `auxclick`. No corresponding `mouseup` | | Safari | 2-finger trackpad click | `mousedown`, `contextmenu` + menu | No `auxclick`. No corresponding `mouseup` | | Chrome | Click | `mousedown`, `mouseup`, `click` | | | Chrome | Ctrl+click | `mousedown`, `contextmenu` + menu | No `auxclick`. No corresponding `mouseup` | | Chrome | 2-finger trackpad click | `mousedown`, `contextmenu` + menu | No `auxclick`. No corresponding `mouseup` | Again, Firefox has the most consistent behavior. Safari and Chrome produce `mousedown` events without corresponding `mouseup` events. Whether or not the context menu is shown (i.e.: whether or not the default actions occurs) should not affect the `auxclick` event. So Firefox's behavior seems correct here. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents/issues/265#issuecomment-652150467
Received on Wednesday, 1 July 2020 02:31:22 UTC