html.elements.dialog - closedby=any bugs for touch
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
What type of issue is this?
Browser bug (a bug with a feature that may impact site compatibility)
What information was incorrect, unhelpful, or incomplete?
Dialog's light dismiss (closedby="any") has bugs in Chrome and Firefox. When using a touch device (or touch emulation devtools), the dismissal tap propagates to elements behind the backdrop, such as a button.
What browsers does this problem apply to, if applicable?
Chromium (Chrome, Edge 79+, Opera, Samsung Browser), Firefox
What did you expect to see?
I expect the touch/tap to dismiss the dialog but not click any elements on the page.
Did you test this? If so, how?
Tested in Firefox v156 and Chrome v153 via DevTools touch emulation, and Android Chrome v152.
The example on MDN for Dialog — Comparison of different closedby behaviors demonstrates the issue.
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
Chrome: https://issues.chromium.org/issues/425579196
Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=2022750
Do you have anything more you want to share?
Chrome v154 will fix the bug: https://chromestatus.com/feature/6209615938322432
MDN URL
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/dialog
MDN metadata
MDN page report details
- Query:
html.elements.dialog - Report started: 2026-09-10T23:49:43.868Z
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the html.elements.dialog compatibility entry linked from the MDN page and review the closedby="any" data for Chromium and Firefox. Compare the recorded support with the touch-dismiss behavior and the linked browser reports, then run the repository's compatibility-data validation. Done means the entry accurately reflects the reported browser behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100