Canvas discards secondary-click ipad

Title: Canvas discards secondary-click (button=2, pointerType=mouse) from trackpad/mouse in Safari on iPadOS — pointing device misclassified as touch

Describe in detail the bug/issue

Figma Design (and FigJam) in Safari on iPadOS no longer opens the canvas context menu on right-click from a connected pointing device (Magic Keyboard trackpad or Magic Mouse). Right-click continues to work in the Layers panel and in all Figma menus. The two-finger-tap context menu on the canvas also still works. Only the pointer-device path on the canvas is broken.

This is not a view-only or permissions state: the canvas is fully editable in the same session (select, move, draw, edit all work). It previously worked in the same browser with the same hardware, so this is a regression.

I have isolated the cause outside Figma. A plain HTML page with a <canvas> element, loaded in the same Safari session, receives a complete, correctly tagged secondary-click sequence from the trackpad:

pointerdown  button=2 buttons=2 pointerType=mouse isPrimary=true
mousedown    button=2 buttons=2
contextmenu  button=2 buttons=2 pointerType=mouse isPrimary=true
pointerup    button=2 buttons=0 pointerType=mouse
mouseup      button=2 buttons=0
auxclick     button=2 buttons=0 pointerType=mouse

WebKit is delivering the event. Figma receives it and does nothing with it on the canvas.

The device signals that differ from macOS Safari are the likely trigger:

userAgent:          identical to macOS Safari (Macintosh; Intel Mac OS X 10_15_7)
maxTouchPoints:     5
(hover: hover):     no
(pointer: fine):    no
(any-pointer: fine): yes

iPadOS reports the primary pointer as coarse even with a trackpad attached, while reporting that a fine pointer is available. If the editor gates the canvas context menu on maxTouchPoints > 0 or on (pointer: fine) / (hover: hover), it classifies the device as touch-only and discards the secondary button. The correct signal is (any-pointer: fine) or, better, the pointerType on the event itself — both of which report a mouse here.

Supporting detail: iPadOS does not emit a contextmenu event for a two-finger tap (it synthesises a meta+click). Since that gesture still opens Figma’s canvas menu, the editor is maintaining its own touch path for the context menu while dropping the standard, spec-compliant mouse path.

Consistently reproducible? Yes — 100%, every file, every team, both devices. Figma support (Alberto, Technical Quality) reproduced it independently on an iPad in a new Design file. No error messages; nothing in the console.

Reproduction steps:

1. iPad with Magic Keyboard (or Magic Mouse) connected.
2. Open any Figma Design file in Safari (not the Figma iPad app). Confirm the canvas is editable.
3. Right-click on the canvas using the trackpad or mouse. → No context menu.
4. Right-click on a layer in the Layers panel. → Context menu opens normally.
5. Two-finger tap the canvas on the screen. → Context menu opens normally.
6. Same account, same file, Chrome on macOS. → Right-click on canvas works.

Product: Figma Design and FigJam (canvas in both). Tags: figma-design, figjam, ipad, safari, bug.

Screenshots, videos, files, logs

• Original report with videos of the behaviour (canvas vs Layers panel, trackpad and Magic Mouse): https://forum.figma.com/report-a-problem-6/right-click-stopped-working-on-figma-canvas-on-ipad-57178
• Support ticket reference: Technical Quality team, handled by Alberto, Oct 2026 — the “working as designed / view only” classification I’m disputing.
• Test file previously shared with support-share@figma.com (view access).

Browser, desktop app or both?

Safari on iPadOS only. Not the Figma iPad app (which I understand is a limited viewer and is out of scope here). Not reproducible on macOS Chrome. 

OS / browser version

• iPad Pro M5 (11-inch)
• iPadOS 26.6
• Safari, reporting as Version/27.2 Safari/605.1.15
• Magic Keyboard trackpad and Magic Mouse (both affected)

Troubleshooting already done

• Confirmed on every file and across the account — not file-specific.
• Confirmed on two separate pointing devices.
• Confirmed same account works on macOS Chrome.
• Confirmed the canvas is editable (rules out the view-only explanation).
• Verified with an independent test page that WebKit delivers contextmenu with button=2, pointerType=mouse to a <canvas> element — the event is not being blocked by the browser.
• Reproduced by Figma support on their own iPad in a fresh file (rules out account/file/cache state).
• Cleared Safari cache / tried a private window / no content blockers or extensions active / tried another WebKit browser on the iPad.