- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 May 2019 07:09:53 +0000
- To: public-css-archive@w3.org
We stopped including style containment in strict containment, and marked it at risk, but haven't changed how it works, so it's expected that this sentence would be unchanged. If there's something wrong with it, it feels like a separate issue. But that sentence doesn't seem wrong to me. If you're changing a property, such as changing the `content` property from `none` to `open-quote`on a descendant of the containing element, without style containment, you have to check on the tree outside the containing element if there are other uses of `content` that generate quotes, as they may have to be recalculated. With style containment on, you don't. So that sentence seems correct. You don't this so? -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3280#issuecomment-496392931 using your GitHub account
Received on Tuesday, 28 May 2019 07:09:55 UTC