Closed Bug 1640189 Opened 10 months ago Closed 9 months ago

Firefox Touch Simulation causes click events to not be dispatched on buttons in the Shadow DOM


(DevTools :: Responsive Design Mode, defect, P3)

76 Branch


(Not tracked)



(Reporter: ldebeasi, Unassigned)


(Blocks 1 open bug)



(1 file)

Attached file Code reproduction

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.61 Safari/537.36

Steps to reproduce:

  1. Open provided code reproduction.
  2. Open Firefox Developer Tools, and go to the "Console" tab.
  3. Enable "Responsive Design Mode", but ensure that "Touch Simulation" is disabled.
  4. Click the square. You should notice a "Button was clicked!" message is logged to the console.
  5. Enable "Touch Simulation".
  6. Click the square. You should notice that the "Button was clicked!" message is not logged to the console.

Actual results:

When Touch Simulation is enabled, the click event is not dispatched on the button.

Expected results:

I would expect that the click event be dispatched on the button regardless of simulation state. The message is logged correctly when running this code sample on a physical mobile device or in Chrome/Safari Dev Tools Responsive Design Mode.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → DOM: Events
Product: Firefox → Core
Component: DOM: Events → Responsive Design Mode
Product: Core → DevTools

Hello, thank you for filing this issue! I can confirm this issue is reproducible in Firefox 76 using the above STR. However, the issue does not occur using a recent version of Firefox Nightly. I believe the recent touch simulation work available there has fixed this.

Blocks: rdm-touch
Severity: -- → S3
Ever confirmed: true
Priority: -- → P3

I can confirm that the issue does not occur using Firefox 78.0a1 (Firefox Nightly). Thank you!

Awesome! I'll resolve this issue as fixed (by Bug 1623941) .

Closed: 9 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.