Contact [email protected] Explainer https://github.com/WICG/display-locking/blob/main/explainers/isvisible.md
Specificationhttps://drafts.csswg.org/cssom-view/#dom-element-isvisible Summary Element.isVisible() returns true if the element is visible, and false if it is not. It checks a variety of factors that would make an element invisible, including display:none, visibility, content-visibility, and opacity. Blink componentBlink>DOM <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EDOM> TAG reviewhttps://github.com/w3ctag/design-reviews/issues/734 TAG review statusPending Risks Interoperability and Compatibility This feature is not particularly contentious or complicated, but is mostly useful in the presence of content-visibility. Gecko: No signal WebKit: No signal Web developers: No signals Other signals: Ergonomics This feature could be used in tandem with content-visibility or details elements. Usage of this API will not make it hard for Chrome to maintain good performance. Activation This feature is easy to feature detect and polyfill. Security I have no security risks/considerations for this feature. 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? This does not deprecate or change any existing APIs and does not have any risk for WebView. Debuggability This feature does not need any new debugging features. Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> ?Yes Flag name--enable-blink-features=isVisible Requires code in //chrome?False Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1309533 Estimated milestones 103 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). https://github.com/w3c/csswg-drafts/issues/7232 Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5163102852087808 Links to previous Intent discussionsIntent to prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAK6btwK01yGZ0LVb6M_8WdeC5OM0qfUv5T1TUO%3D1if1G%2BKogRw%40mail.gmail.com <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAK6btwK01yGZ0LVb6M_8WdeC5OM0qfUv5T1TUO=1if1g+ko...@mail.gmail.com> 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/CAK6btw%2BVuGFBfV_Y1ZfdBNryax0u1ykmeK-RzEXt11%2BEFn8iUg%40mail.gmail.com.
