LGTM1

On 8/7/25 4:31 p.m., Joey Arhar wrote:


        Contact emails

jar...@chromium.org


        Explainer

None


        Specification

https://github.com/whatwg/html/pull/11457


        Summary

The spec recently had some small changes to the revealing algorithms for hidden=until-found and details elements in order to prevent the browser from getting stuck in an infinite loop: https://github.com/whatwg/html/pull/11457



        Blink component

Blink>DOM <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EDOM%22>


        TAG review

None


        TAG review status

Not applicable


        Risks



        Interoperability and Compatibility

None



/Gecko/: Positive (https://bugzilla.mozilla.org/show_bug.cgi?id=1980442) Firefox is implementing: https://github.com/web-platform-tests/interop/issues/984#issuecomment-3164919463

/WebKit/: Shipped/Shipping (https://bugs.webkit.org/show_bug.cgi?id=296797)

/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?

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
        
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?

Yes

https://github.com/web-platform-tests/wpt/pull/54116



        Flag name on about://flags



        Finch feature name

AncestorRevealingNewSpec


        Rollout plan

Will ship enabled for all users


        Requires code in //chrome?

False


        Tracking bug

https://issues.chromium.org/issues/433545121


        Estimated milestones

Shipping on desktop     141
Shipping on Android     141
Shipping on WebView     141



        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/5179013869993984?gate=5101028303306752

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 blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAK6btw%2BJbE5tWwNVVE8c%3DqdnDsYLvUkHkWj2eERWuacTSHGNqg%40mail.gmail.com <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAK6btw%2BJbE5tWwNVVE8c%3DqdnDsYLvUkHkWj2eERWuacTSHGNqg%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 blink-dev+unsubscr...@chromium.org.
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/e01dcb1b-cf80-4991-813a-6aee3ce353de%40chromium.org.

Reply via email to