W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2020

Re: [csswg-drafts] [css-contain-2] apply containment on `content-visibility: visible` ; use `normal` as initial value (#5695)

From: Chris Harrelson via GitHub <sysbot+gh@w3.org>
Date: Mon, 30 Nov 2020 22:02:31 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-736083057-1606773750-sysbot+gh@w3.org>
> @chrishtr We're not taking away any values, just changing 'visible' to have a containment side-effect when set explicitly (rather than as the initial value) and giving the initial value a new name.

Adding a new value is fine, it just needs to be a name that does not break existing content already relying on the current values
in Chromium.

> Generally, you don't want to be flipping containment on/off anyway, right? That impacts layout in significant ways, and the point is to flip visibility without impacting layout, right?

Agreed. The previous "plan of record" my team was going to pursue was `will-change: content-visibility` which would have the same effect, but this works also.



-- 
GitHub Notification of comment by chrishtr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5695#issuecomment-736083057 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 30 November 2020 22:02:34 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:22 UTC