On Tue, May 24, 2022 at 4:38 PM Jihwan Kim <[email protected]> wrote:

> Contact [email protected]
>
> ExplainerNone
>

A short text explaining what the feature is with an example would've gone a
long way to help folks (like me) understand this intent.


>
> Specificationhttps://www.w3.org/TR/selectors-4/#modal-state
>
> Summary
>
> A pseudo class selector to style dialog element.
>

The spec also mentions fullscreen. Is it covered by this intent as well?


> The :modal pseudo-class represents an element which is in a state that
> excludes all interaction with elements outside it until it has been
> dismissed.
>
>
> Blink componentBlink>CSS
> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS>
>
> TAG review
>

I agree that a TAG review may not be necessary here since this is adopted
by the CSSWG and shipped in another engine.


>
>
> TAG review statusPending
>
> Risks
>
>
> Interoperability and Compatibility
>
>
>
> Gecko: Shipped/Shipping (
> https://bugzilla.mozilla.org/show_bug.cgi?id=1768535)
>

That's an open issue, not an indication they shipped this.


>
> WebKit: Shipped/Shipping (https://bugs.webkit.org/show_bug.cgi?id=240109)
>
> Web developers: No signals
>

> 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?
>
>
>
> Debuggability
>
> Automatically supported, same as other pseudo-elements.
>
>
> Is this feature fully tested by web-platform-tests
> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
> ?Yes
>

Link to the WPTs?


>
>
> Flag name
>
> Requires code in //chrome?False
>
> Tracking bughttps://crbug.com/1327113
>
> Estimated milestones
>
> No milestones specified
>
>
> 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).
>
>
> Link to entry on the Chrome Platform Status
> https://chromestatus.com/feature/5192833009975296
>
> This intent message was generated by Chrome Platform Status
> <https://chromestatus.com/>.
>
> --
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPJHA1oU6TM%3DqU6udPJ46g2%3DUoYYiObOuoYrSLboMBZe7icofQ%40mail.gmail.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPJHA1oU6TM%3DqU6udPJ46g2%3DUoYYiObOuoYrSLboMBZe7icofQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfVEWFBSd8QW8MAjd3KuKcViuruefQWc6eQP%2BE4SGRVA9w%40mail.gmail.com.

Reply via email to