Add support for the `contentvisibilityautostatechanged` event
Categories
(Core :: Layout, enhancement)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox110 | --- | fixed |
People
(Reporter: mrobinson, Assigned: mrobinson)
References
(Blocks 1 open bug)
Details
(Keywords: dev-doc-needed)
Attachments
(1 file)
This event tracks changes in relevancy to the content of elements with content-visibility: auto.
See https://w3c.github.io/csswg-drafts/css-contain-2/#content-visibility-auto-state-changed
|
Assignee | |
Comment 1•2 years ago
|
||
Add support for the contentvisibilityautostatechanged and fire it when
the relevancy of content-visibility: auto elements change. This change
also fixes the WPT tests for this event. It was using top to access
an element with id=top even though top refers to the top-level browser
window.
|
||
Updated•1 year ago
|
|
|
||
Updated•1 year ago
|
Pushed by mrobinson@igalia.com: https://hg.mozilla.org/integration/autoland/rev/6095dabf5574 Add support for the `contentvisibilityautostatechange` event r=emilio
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/37573 for changes under testing/web-platform/tests
|
||
Comment 4•1 year ago
|
||
| bugherder | ||
Upstream PR merged by moz-wptsync-bot
MDN work can be tracked here https://github.com/mdn/content/issues/23687
|
||
Updated•1 year ago
|
|
||
Comment 7•1 year ago
|
||
https://github.com/mdn/browser-compat-data/pull/18812 is wrong, as this is still disabled by default: https://searchfox.org/mozilla-central/rev/0e3779abe6ad44feb787a295fbb67bc9fe4e927a/modules/libpref/init/StaticPrefList.yaml#8386-8391
Can you take a second look? Thanks!
|
|
||
Comment 8•1 year ago
|
||
@Kagami - Yes - I fixed it in https://github.com/mdn/browser-compat-data/pull/18865 - posted 2 weeks ago, but only merged 2 days ago - so might not have updated on MDN.
You can also see it in the data here: https://github.com/mdn/browser-compat-data/blob/main/api/ContentVisibilityAutoStateChangeEvent.json#L13-L22
Thanks for keeping a close eye on this. We did initially get it wrong (I just copied the release status for content-visibility: auto which was wrong)
Description
•