- From: Nathan Knowler via GitHub <noreply@w3.org>
- Date: Tue, 28 Apr 2026 20:23:20 +0000
- To: public-css-archive@w3.org
knowler has just submitted a new pull request for https://github.com/w3c/csswg-drafts: == [css-contain-2] `contentvisibilityautostatechange` event should bubble #11310 == Resolves #11310 I believe this was missed as Blink (the first implementer, who I also believe designed the feature?) has the event bubble, while Gecko and WebKit who implemented afterwards, do not bubble per the existing spec. The default for `EventInit` is to not bubble, so that’s part of why I think it was originally missed. There’s been no discussion and therefore no consensus on this… this is just an interop issue that I’ve known of for over a year now that I’d like to stop caveating [everywhere I write about it](https://12daysofweb.dev/2024/css-content-visibility/#:~:text=a%20discrepancy) or use the feature (since a workaround potentially is necessary). Also, not sure if this is how or where this change needs to happen — I’m happy to be directed elsewhere! See https://github.com/w3c/csswg-drafts/pull/13854 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 28 April 2026 20:23:20 UTC