Groups keyboard shortcuts have been updated
Dismiss
See shortcuts

Intent to Ship: Dialog light dismiss

403 views
Skip to first unread message

Mason Freed

unread,
Jan 15, 2025, 11:57:59 AMJan 15
to blink-dev

Contact emails

mas...@chromium.org

Explainer

None

Specification

https://html.spec.whatwg.org/#attr-dialog-closedby

Summary

One of the nice features of the Popover API is its light dismiss behavior. This chromestatus is about bringing that same capability to `<dialog>`. A new `closedby` attribute controls behavior: `<dialog closedby=none>` - no user-triggered closing of dialogs at all. `<dialog closedby=closerequest>` - user pressing ESC (or other close trigger) closes the dialog `<dialog closedby=any>` - user clicking outside the dialog, or pressing ESC, closes the dialog. Akin to `popover=auto` behavior.



Blink component

Blink>DOM

Search tags

dialog, light dismiss

TAG review

None

TAG review status

Not applicable

Risks



Interoperability and Compatibility

None



Gecko: No signal (https://github.com/mozilla/standards-positions/issues/998)

WebKit: No signal (https://github.com/WebKit/standards-positions/issues/329)

Web developers: Strongly positive

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

None



Debuggability

None



Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?

Yes

Is this feature fully tested by web-platform-tests?

Yes

https://wpt.fyi/results/html/semantics/interactive-elements/the-dialog-element?label=master&label=experimental&aligned&q=closedby



Flag name on about://flags

HTMLDialogLightDismiss

Finch feature name

HTMLDialogLightDismiss

Requires code in //chrome?

False

Tracking bug

https://crbug.com/376516550

Estimated milestones

Shipping on desktop134
DevTrial on desktop133
Shipping on Android134
DevTrial on Android133
Shipping on WebView134


Anticipated spec changes

Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).

None

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5097714453577728?gate=5165153493188608

Links to previous Intent discussions

Intent to Prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/eDXEmWB7Xo8/m/3ZsbU8AwBgAJ


This intent message was generated by Chrome Platform Status.

Mike Taylor

unread,
Jan 22, 2025, 6:39:40 AMJan 22
to Mason Freed, blink-dev

LGTM1

On 1/15/25 5:57 PM, Mason Freed wrote:

Contact emails

mas...@chromium.org

Explainer

None

Specification

https://html.spec.whatwg.org/#attr-dialog-closedby

Summary

One of the nice features of the Popover API is its light dismiss behavior. This chromestatus is about bringing that same capability to `<dialog>`. A new `closedby` attribute controls behavior: `<dialog closedby=none>` - no user-triggered closing of dialogs at all. `<dialog closedby=closerequest>` - user pressing ESC (or other close trigger) closes the dialog `<dialog closedby=any>` - user clicking outside the dialog, or pressing ESC, closes the dialog. Akin to `popover=auto` behavior.



Blink component

Blink>DOM

Search tags

dialog, light dismiss

TAG review

None

TAG review status

Not applicable

Risks



Interoperability and Compatibility

None



Gecko: No signal (https://github.com/mozilla/standards-positions/issues/998)

WebKit: No signal (https://github.com/WebKit/standards-positions/issues/329)
The WebKit position is trending positive, based on https://github.com/WebKit/standards-positions/issues/329#issuecomment-2604702351.

Web developers: Strongly positive

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

None



Debuggability

None



Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?

Yes

Is this feature fully tested by web-platform-tests?

Yes

https://wpt.fyi/results/html/semantics/interactive-elements/the-dialog-element?label=master&label=experimental&aligned&q=closedby

Given that the PR landed in HTML, can we remove .tentative from the tests?
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDh3596VtU3%3DcdGU%2BMoPCrU2APkgn2ji8qPzXKwqqVJJBQ%40mail.gmail.com.

Vladimir Levin

unread,
Jan 22, 2025, 9:30:55 AMJan 22
to Mike Taylor, Mason Freed, blink-dev
LGTM2

I think this is an extremely useful attribute, so I don't doubt that web developers signal is strongly positive, but is there any evidence you can point to?

Thanks,
Vlad
 

Yoav Weiss (@Shopify)

unread,
Jan 22, 2025, 9:38:56 AMJan 22
to blink-dev, Vladimir Levin, Mason Freed, blink-dev, Mike Taylor
LGTM3

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

Mason Freed

unread,
Jan 22, 2025, 12:14:13 PMJan 22
to Yoav Weiss (@Shopify), blink-dev, Vladimir Levin, Mike Taylor
Thank you all! A few replies below...

On Wed, Jan 22, 2025 at 6:39 AM Yoav Weiss (@Shopify) <yoav...@chromium.org> wrote:
LGTM3

On Wednesday, January 22, 2025 at 3:30:55 PM UTC+1 Vladimir Levin wrote:
LGTM2

I think this is an extremely useful attribute, so I don't doubt that web developers signal is strongly positive, but is there any evidence you can point to?

I have a lot of anecdotal evidence (people excited about it), but fewer bits of concrete data. There was a high level of engagement on the WHATWG and OpenUI issues discussing this feature, so perhaps that helps?

On Wed, Jan 22, 2025 at 6:39 AM Mike Taylor <mike...@chromium.org> wrote:

LGTM1

The WebKit position is trending positive, based on https://github.com/WebKit/standards-positions/issues/329#issuecomment-2604702351.

Yep, thanks.
 
Given that the PR landed in HTML, can we remove .tentative from the tests?

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
Reply all
Reply to author
Forward
0 new messages