Add dialog light dismiss behavior #10737

mfreed7 · 2024-10-31T23:17:09Z

This adds a few things:

A closedby attribute that can be used to control the light dismiss behavior of dialogs:
1. <dialog closedby=none> - no user-triggered closing of dialogs at all.
2. <dialog closedby=closerequest> - user pressing ESC (or other close trigger) closes the dialog
3. <dialog closedby=any> - user clicking outside the dialog, or pressing ESC, closes the dialog. Akin to popover=auto behavior.
4. <dialog> - i.e. no closedby attribute - default/old behavior. Behaves like closedby=closerequest for modal dialogs, and closedby=none for modeless dialogs.
This PR also (per the request) adds a dialog.requestClose() which fires the cancel event, and then (if that isn't cancelled) fires the close event and closes the dialog.
I also consolidated the "light dismiss" activities into one algorithm, which will need to be called by Add popover light dismiss integration w3c/pointerevents#460 if that ever gets some attention.

Some interesting related links:

WIP dialog closedby attribute spec #10157 - much of this PR was lifted from @lukewarlow's PR
Add light dismiss functionality to <dialog> #9373 - the WHATWG discussion
Bikeshed a name for "light dismiss for dialog" openui/open-ui#834 - the OpenUI discussion
Naming for the *attribute* to enable "light dismiss for dialog" openui/open-ui#960 - naming discussion to get to closedby
Naming for the *value* for the attribute that means "just close with ESC" openui/open-ui#961 - naming discussion to get to closerequest

At least two implementers are interested (and none opposed):
- Chromium
- WebKit: Presumably supportive, based on @annevk reviews. No official position
- Gecko: @smaug---- has said he would review, so TBD. No official position
Tests are written and can be reviewed and commented upon at:
- https://wpt.fyi/results/html/semantics/interactive-elements/the-dialog-element?label=master&label=experimental&aligned&q=dialog-closedby.tentative.html%20or%20dialog-popover-closedby-complex.tentative.html%20or%20dialog-popover-closedby-simple.tentative.html%20or%20dialog-requestclose.tentative.html
Implementation bugs are filed:
- Chromium: https://crbug.com/376516550
- Gecko: https://bugzilla.mozilla.org/show_bug.cgi?id=1936940
- WebKit: https://bugs.webkit.org/show_bug.cgi?id=284592
MDN issue is filed: Add documentation of new dialog light dismiss behaviors mdn/content#37196
The top of this comment includes a clear commit message to use.

(See WHATWG Working Mode: Changes for more details.)

/dnd.html ( diff )
/dom.html ( diff )
/index.html ( diff )
/indices.html ( diff )
/infrastructure.html ( diff )
/interaction.html ( diff )
/interactive-elements.html ( diff )
/popover.html ( diff )
/semantics-other.html ( diff )

domenic · 2024-11-01T08:14:59Z

This is exciting! Unfortunately I am going OOO for a week starting ~now, so won't get a chance to review too soon. Hopefully others will be able to help with some reviews, but I would like to get a chance to carefully review the close watcher integration, etc. before this lands.

Would you mind commenting on what approach you took to the mutability of the closedby attribute? We discussed that a bit in #9373, and I think we came up with a tentative proposal, but I'm not sure it was battle-tested.

keithamus · 2024-11-01T12:03:59Z

Would you mind commenting on what approach you took to the mutability of the closedby attribute? We discussed that a bit in #9373, and I think we came up with a tentative proposal, but I'm not sure it was battle-tested.

Looks like CloseWatchers get a mutable enabled value, which is toggled whenever closedby is set to the applicable values - when false it skips the events and returns early. IMO this seems to nicely side-skirt the stacking issues around mutation of the attribute without adding lots of complexity in either the consuming elements and/or having some messy algorithms to insert mid-way into a stack.

keithamus

This looks great to me!

source

mfreed7 · 2024-11-01T16:07:01Z

This is exciting! Unfortunately I am going OOO for a week starting ~now, so won't get a chance to review too soon. Hopefully others will be able to help with some reviews, but I would like to get a chance to carefully review the close watcher integration, etc. before this lands.

That's totally fine - no rush. I did this one in the opposite order that I usually do: spec first, prototype after. So I'm moving on to prototype it now, which might reveal other flaws. But I thought since @lukewarlow had gotten the spec into such decent shape, that I'd clean it up and open the PR in case folks saw other flaws there that I could address in the prototype.

Would you mind commenting on what approach you took to the mutability of the closedby attribute? We discussed that a bit in #9373, and I think we came up with a tentative proposal, but I'm not sure it was battle-tested.

As @keithamus said, I just kept what @lukewarlow did in the original PR, and used a new enabled state on CloseWatcher. I haven't implemented that yet, but it seems reasonably straightforward. But let me know if you see any flaws.

source

annevk · 2024-11-05T09:59:35Z

source

+  <p>The <code data-x="attr-dialog-closedby">closedby</code> attribute's <i data-x="invalid value
+  default">invalid value default</i> and <i data-x="missing value default">missing value
+  default</i> are both the <dfn data-x="attr-closedby-auto-state">Auto</dfn> state. The <span
+  data-x="attr-closedby-auto-state">auto</span> state matches <span
+  data-x="attr-closedby-closerequest-state">closerequest</span> when the element is modal;
+  otherwise <span data-x="attr-closedby-none-state">none</span>.</p>


There's very inconsistent spelling of states here. They should match the capitalization and words of how they are introduced. And should typically be followed by the word state (though that's not linked).

Also, perhaps the statement of fact is better as a note?

There's very inconsistent spelling of states here. They should match the capitalization and words of how they are introduced. And should typically be followed by the word state (though that's not linked).

Yep, I agree. I fixed them all up, I think. Please let me know if you see any others I missed. All are now lowercase.

Also, perhaps the statement of fact is better as a note?

Sorry - can you help me understand this? Which "statement of fact"?

This CL puts the feature flag in place, adds (flag guarded) closedBy and requestClose() methods to <dialog>, connects the pointer events handling to a new dialog light dismiss method, and adds a basic set of tests. None of the actual functionality is here yet, this is just a shell. Subsequent CLs will flesh out the behavior. See spec PR for details: whatwg/html#10737 Here's the chromestatus: https://chromestatus.com/feature/5097714453577728 Bug: 376516550 Change-Id: I3727ca21476a2a3340fd18597970395d64ef7176

This CL puts the feature flag in place, adds (flag guarded) closedBy and requestClose() methods to <dialog>, connects the pointer events handling to a new dialog light dismiss method, and adds a basic set of tests. None of the actual functionality is here yet, this is just a shell. Subsequent CLs will flesh out the behavior. See spec PR for details: whatwg/html#10737 Here's the chromestatus: https://chromestatus.com/feature/5097714453577728 Bug: 376516550 Change-Id: I3727ca21476a2a3340fd18597970395d64ef7176 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5985491 Commit-Queue: Mason Freed <[email protected]> Reviewed-by: David Baron <[email protected]> Cr-Commit-Position: refs/heads/main@{#1378633}

This implements reflection of `closedBy` including the "limited to known values" behavior. See spec PR for details: whatwg/html#10737 Bug: 376516550 Change-Id: Iddefd573fe19fd39f4b3aebe13390235fea969b9

…ht dismiss [1/N], a=testonly Automatic update from web-platform-tests Implement basic structure for dialog light dismiss [1/N] This CL puts the feature flag in place, adds (flag guarded) closedBy and requestClose() methods to <dialog>, connects the pointer events handling to a new dialog light dismiss method, and adds a basic set of tests. None of the actual functionality is here yet, this is just a shell. Subsequent CLs will flesh out the behavior. See spec PR for details: whatwg/html#10737 Here's the chromestatus: https://chromestatus.com/feature/5097714453577728 Bug: 376516550 Change-Id: I3727ca21476a2a3340fd18597970395d64ef7176 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5985491 Commit-Queue: Mason Freed <[email protected]> Reviewed-by: David Baron <[email protected]> Cr-Commit-Position: refs/heads/main@{#1378633} -- wpt-commits: 1d5037cc3ff4524fd5d9f1a461afd20aebbb0839 wpt-pr: 48976

This implements reflection of `closedBy` including the "limited to known values" behavior. See spec PR for details: whatwg/html#10737 Bug: 376516550 Change-Id: Iddefd573fe19fd39f4b3aebe13390235fea969b9

This implements reflection of `closedBy` including the "limited to known values" behavior. See spec PR for details: whatwg/html#10737 Bug: 376516550 Change-Id: Iddefd573fe19fd39f4b3aebe13390235fea969b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5988652 Commit-Queue: Mason Freed <[email protected]> Reviewed-by: David Baron <[email protected]> Commit-Queue: David Baron <[email protected]> Auto-Submit: Mason Freed <[email protected]> Cr-Commit-Position: refs/heads/main@{#1379228}

This enables `closedby=none` to *stop* the dialog from closing when the ESC key (or other close signal) is received. See spec PR for details: whatwg/html#10737 Bug: 376516550 Change-Id: I0bf7fc7a50acaffb89e183fe6e19f411de4da576 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5990171 Reviewed-by: David Baron <[email protected]> Commit-Queue: Mason Freed <[email protected]> Cr-Commit-Position: refs/heads/main@{#1379279}

…ht dismiss [1/N], a=testonly Automatic update from web-platform-tests Implement basic structure for dialog light dismiss [1/N] This CL puts the feature flag in place, adds (flag guarded) closedBy and requestClose() methods to <dialog>, connects the pointer events handling to a new dialog light dismiss method, and adds a basic set of tests. None of the actual functionality is here yet, this is just a shell. Subsequent CLs will flesh out the behavior. See spec PR for details: whatwg/html#10737 Here's the chromestatus: https://chromestatus.com/feature/5097714453577728 Bug: 376516550 Change-Id: I3727ca21476a2a3340fd18597970395d64ef7176 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5985491 Commit-Queue: Mason Freed <[email protected]> Reviewed-by: David Baron <[email protected]> Cr-Commit-Position: refs/heads/main@{#1378633} -- wpt-commits: 1d5037cc3ff4524fd5d9f1a461afd20aebbb0839 wpt-pr: 48976

…alog closedBy [2/N], a=testonly Automatic update from web-platform-tests Add attribute reflection behavior for dialog closedBy [2/N] This implements reflection of `closedBy` including the "limited to known values" behavior. See spec PR for details: whatwg/html#10737 Bug: 376516550 Change-Id: Iddefd573fe19fd39f4b3aebe13390235fea969b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5988652 Commit-Queue: Mason Freed <[email protected]> Reviewed-by: David Baron <[email protected]> Commit-Queue: David Baron <[email protected]> Auto-Submit: Mason Freed <[email protected]> Cr-Commit-Position: refs/heads/main@{#1379228} -- wpt-commits: 28946b88d5b2e037bb2506ae4984e8725ba5560b wpt-pr: 48989

This implements dialog.requestClose() and adds a test. See spec PR for details: whatwg/html#10737 Bug: 376516550 Change-Id: Iaac3d89c28844d2b54ff5b1a7b68dc356d1fd172

source

Per the conversation here: openui/open-ui#1128 (comment) There's a desire to ship closeWatcher.requestClose() along with dialog.requestclose() both not requiring user activation. The spec PR has been updated accordingly: whatwg/html#10737 (in this commit: whatwg/html@76619aa) Fixed: 383593252 Change-Id: I8c05e352d8b4964407a1cee36f35372e192e2ca5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6092173 Auto-Submit: Mason Freed <[email protected]> Reviewed-by: David Baron <[email protected]> Reviewed-by: Mason Freed <[email protected]> Commit-Queue: Mason Freed <[email protected]> Cr-Commit-Position: refs/heads/main@{#1396007}

…uire user activation, a=testonly Automatic update from web-platform-tests Make closeWatcher.requestClose() not require user activation Per the conversation here: openui/open-ui#1128 (comment) There's a desire to ship closeWatcher.requestClose() along with dialog.requestclose() both not requiring user activation. The spec PR has been updated accordingly: whatwg/html#10737 (in this commit: whatwg/html@76619aa) Fixed: 383593252 Change-Id: I8c05e352d8b4964407a1cee36f35372e192e2ca5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6092173 Auto-Submit: Mason Freed <[email protected]> Reviewed-by: David Baron <[email protected]> Reviewed-by: Mason Freed <[email protected]> Commit-Queue: Mason Freed <[email protected]> Cr-Commit-Position: refs/heads/main@{#1396007} -- wpt-commits: 36042af16ff7ebcbf7ed2b12401a10939d5842a0 wpt-pr: 49681

…uire user activation, a=testonly Automatic update from web-platform-tests Make closeWatcher.requestClose() not require user activation Per the conversation here: openui/open-ui#1128 (comment) There's a desire to ship closeWatcher.requestClose() along with dialog.requestclose() both not requiring user activation. The spec PR has been updated accordingly: whatwg/html#10737 (in this commit: whatwg/html@76619aa) Fixed: 383593252 Change-Id: I8c05e352d8b4964407a1cee36f35372e192e2ca5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6092173 Auto-Submit: Mason Freed <masonfchromium.org> Reviewed-by: David Baron <dbaronchromium.org> Reviewed-by: Mason Freed <masonfchromium.org> Commit-Queue: Mason Freed <masonfchromium.org> Cr-Commit-Position: refs/heads/main{#1396007} -- wpt-commits: 36042af16ff7ebcbf7ed2b12401a10939d5842a0 wpt-pr: 49681 UltraBlame original commit: c689e198a6664efd81b4283aa8a7f19430c37c07

…uire user activation, a=testonly Automatic update from web-platform-tests Make closeWatcher.requestClose() not require user activation Per the conversation here: openui/open-ui#1128 (comment) There's a desire to ship closeWatcher.requestClose() along with dialog.requestclose() both not requiring user activation. The spec PR has been updated accordingly: whatwg/html#10737 (in this commit: whatwg/html@76619aa) Fixed: 383593252 Change-Id: I8c05e352d8b4964407a1cee36f35372e192e2ca5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6092173 Auto-Submit: Mason Freed <[email protected]> Reviewed-by: David Baron <[email protected]> Reviewed-by: Mason Freed <[email protected]> Commit-Queue: Mason Freed <[email protected]> Cr-Commit-Position: refs/heads/main@{#1396007} -- wpt-commits: 36042af16ff7ebcbf7ed2b12401a10939d5842a0 wpt-pr: 49681

mfreed7 · 2025-01-09T17:55:22Z

Gentle ping on this PR. All checkboxes are checked and it has an editor approval.

lukewarlow · 2025-01-09T18:32:20Z

Fwiw regarding implementor interest I raised mozilla/standards-positions#998 and WebKit/standards-positions#329

mfreed7 · 2025-01-09T19:47:49Z

Fwiw regarding implementor interest I raised mozilla/standards-positions#998 and WebKit/standards-positions#329

Oh, thanks! I didn't realize those had been filed. I added them to the OP block.

domenic · 2025-01-15T05:00:05Z

Back from vacation, and merged! Please remember to send a PR renaming the tests from .tentative.

stof · 2025-01-15T13:11:04Z

Would closedBy=any also close when clicking on the backdrop pseudo-element or is it not considered a click outside the dialog ?

lukewarlow · 2025-01-15T13:24:31Z

Would closedBy=any also close when clicking on the backdrop pseudo-element or is it not considered a click outside the dialog ?

Yes, that closes the dialog. Here's a demo you can play around with in Chrome canary (w/ experimental web flag): https://jsfiddle.net/vco1mdth/

lukewarlow · 2025-01-15T15:28:07Z

PR to remove tentative from tests at web-platform-tests/wpt#50100

mfreed7 · 2025-01-15T16:45:19Z

Back from vacation, and merged! Please remember to send a PR renaming the tests from .tentative.

Welcome back, and thanks!

keithamus reviewed Nov 1, 2024

View reviewed changes

source Outdated Show resolved Hide resolved

mfreed7 mentioned this pull request Nov 1, 2024

Support disabling CloseWatcher integration in <dialog> #10592

Closed

annevk added addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest needs tests Moving the issue forward requires someone to write tests topic: dialog The <dialog> element labels Nov 5, 2024

annevk reviewed Nov 5, 2024

View reviewed changes

source Outdated Show resolved Hide resolved

annevk reviewed Nov 5, 2024

View reviewed changes

mfreed7 mentioned this pull request Nov 5, 2024

Add light dismiss functionality to <dialog> #9373

Closed

chromium-wpt-export-bot mentioned this pull request Nov 5, 2024

Implement basic structure for dialog light dismiss [1/N] web-platform-tests/wpt#48976

Merged

chromium-wpt-export-bot mentioned this pull request Nov 5, 2024

Add attribute reflection behavior for dialog closedBy [2/N] web-platform-tests/wpt#48989

Merged

chromium-wpt-export-bot mentioned this pull request Nov 8, 2024

Implement dialog.requestClose() [4/N] web-platform-tests/wpt#49050

Merged

annevk reviewed Nov 8, 2024

View reviewed changes

past mentioned this pull request Dec 13, 2024

Upcoming WHATNOT meeting on 2024-12-12 #10825

Closed

mfreed7 mentioned this pull request Dec 13, 2024

Add documentation of new dialog light dismiss behaviors mdn/content#37196

Open

chromium-wpt-export-bot mentioned this pull request Dec 13, 2024

Make closeWatcher.requestClose() not require user activation web-platform-tests/wpt#49681

Merged

mkrause mentioned this pull request Jan 5, 2025

Top layer (dialog, popover) browser limitations fortanix/baklava#88

Open

mfreed7 mentioned this pull request Jan 10, 2025

[interest invokers] How to define/control the action on "losing interest" openui/open-ui#1064

Closed

domenic merged commit 8029d4f into whatwg:main Jan 15, 2025
2 checks passed

domenic added normative change topic: close watchers and removed needs implementer interest Moving the issue forward requires implementers to express interest needs tests Moving the issue forward requires someone to write tests labels Jan 15, 2025

YusukeHirao mentioned this pull request Jan 15, 2025

Supporting for <dialog closedby> attribute markuplint/markuplint#2378

Open

lukewarlow mentioned this pull request Jan 15, 2025

Remove tentative from dialog closedby attribute and requestClose web-platform-tests/wpt#50100

Merged

This was referenced Jan 16, 2025

Upcoming WHATNOT meeting on 2025-01-16 #10906

Open

Dialog light dismiss PR contains source comment that should have been removed #10918

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add dialog light dismiss behavior #10737

Add dialog light dismiss behavior #10737

mfreed7 commented Oct 31, 2024 •

edited by pr-preview bot

Loading

domenic commented Nov 1, 2024

keithamus commented Nov 1, 2024

keithamus left a comment

mfreed7 commented Nov 1, 2024

annevk Nov 5, 2024

annevk Nov 5, 2024

mfreed7 Nov 8, 2024

mfreed7 commented Jan 9, 2025

lukewarlow commented Jan 9, 2025

mfreed7 commented Jan 9, 2025

domenic commented Jan 15, 2025

stof commented Jan 15, 2025

lukewarlow commented Jan 15, 2025

lukewarlow commented Jan 15, 2025

mfreed7 commented Jan 15, 2025

Add dialog light dismiss behavior #10737

Add dialog light dismiss behavior #10737

Conversation

mfreed7 commented Oct 31, 2024 • edited by pr-preview bot Loading

domenic commented Nov 1, 2024

keithamus commented Nov 1, 2024

keithamus left a comment

Choose a reason for hiding this comment

mfreed7 commented Nov 1, 2024

annevk Nov 5, 2024

Choose a reason for hiding this comment

annevk Nov 5, 2024

Choose a reason for hiding this comment

mfreed7 Nov 8, 2024

Choose a reason for hiding this comment

mfreed7 commented Jan 9, 2025

lukewarlow commented Jan 9, 2025

mfreed7 commented Jan 9, 2025

domenic commented Jan 15, 2025

stof commented Jan 15, 2025

lukewarlow commented Jan 15, 2025

lukewarlow commented Jan 15, 2025

mfreed7 commented Jan 15, 2025

mfreed7 commented Oct 31, 2024 •

edited by pr-preview bot

Loading