-
Notifications
You must be signed in to change notification settings - Fork 22.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FF122 ExprFeatre: Element.checkVisibility() supports options.contentVisibilityAuto #31215
FF122 ExprFeatre: Element.checkVisibility() supports options.contentVisibilityAuto #31215
Conversation
Preview URLs Flaws (1)URL:
External URLs (2)URL:
(comment last updated: 2024-01-08 00:01:42) |
…isibilityAuto property
b93a74c
to
be52f66
Compare
@pepelsbey I'm away for a couple of weeks from tomorrow so if you can't look at this today I won't be here to respond to any review comments. If the comments are just editorial, please integrate and self-merge. I will also try find someone else to look at this today in case you are away still. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
…isibilityAuto (mdn#31215) * FF122 ExprFeatre: Element.checkVisibility() supports options.contentVisibilityAuto property * Update files/en-us/mozilla/firefox/experimental_features/index.md
…isibilityAuto (mdn#31215) * FF122 ExprFeatre: Element.checkVisibility() supports options.contentVisibilityAuto property * Update files/en-us/mozilla/firefox/experimental_features/index.md
FF122 adds support to get whether an element's rendering is been skipped due to
content-visibility:auto
being set. The support is a new property of theElement.checkVisibility()
options parameter object namedcontentVisibilityAuto
. There are also two other optionsopacityProperty
andvisibilityProperty
created as aliases of other existing options in the same bugzilla https://bugzilla.mozilla.org/show_bug.cgi?id=1859852There are two complications:
checkVisibility()
will always return the correct value even now (because it will befalse
if not in preview).So I think these new options are effectively released, but I'm not sure, and I'm in discussion with BCD/engineering.
For now I have put all these options in experimental features associated with the
content-visibility:auto
information. I would have some of this information here in any case. But I may need to move some of it to release notes depending on how the discussion falls out with BCD team.Other docs work for this can be tracked in #31107