Intent to Prototype: checkVisibility: contentVisibilityAuto, opacityProperty, and visibilityProperty

[Vladimir Levin]

Contact emails

vmp...@chromium.org

Specification

https://drafts.csswg.org/cssom-view/#dom-element-checkvisibility

Summary

This feature adds three more values to the checkVisibility (https://drafts.csswg.org/cssom-view/#dom-element-checkvisibility) dictionary members: * opacityProperty as an alias for checkOpacity * visibilityProperty as an alias for checkVisibilityCSS * contentVisibilityAuto as a property that allows checking whether an element is in a subtree skipped by content-visibility: auto.

Blink component

Blink>DOM

TAG review

None, this is a small addition to an existing API. It doesn't seem necessary for a TAG review. Please let me know if you believe otherwise.

TAG review status

Not applicable

Risks

Interoperability and Compatibility

None. There is a low risk of interop or compat risks, since this is an addition to an existing API that doesn't change existing usages

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

WebKit: Positive (https://github.com/w3c/csswg-drafts/issues/9487#issuecomment-1782109845) The naming proposal came from Safari

Web developers: No signals

Other signals:

Ergonomics

There are no ergonomic risks, since this adds extra properties to an existing feature.

Activation

There are no activation risks, since this adds extra (useful) properties to an existing feature

Security

There are no extra security issues here that were not already considered during the checkVisibility review.

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

This would be debugged as any other script APIs

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

Yes

Will write tests as a part of the implementation

Flag name on chrome://flags

Finch feature name

CheckVisibilityExtraProperties

Requires code in //chrome?

False

Estimated milestones

Shipping on desktop	121
DevTrial on desktop	121

Shipping on Android	121
DevTrial on Android	121

Shipping on WebView

121

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/pull/9549

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5070043440480256

This intent message was generated by Chrome Platform Status.