- From: vmpstr via GitHub <sysbot+gh@w3.org>
- Date: Thu, 19 Aug 2021 19:47:35 +0000
- To: public-css-archive@w3.org
vmpstr has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-contain] Should scrollIntoView scroll to content-visibility: hidden subtree elements == [content-visibility: hidden](https://www.w3.org/TR/css-contain-2/#content-visibility) property skips its contents and notably says that they shouldn't be available to user agent features like find-in-page nor should they be focusable and selectable. It also says that if the layout work is done, then the user-agent should retain as much of that state as possible in order to make revealing the contents faster. [scrollIntoView()](https://drafts.csswg.org/cssom-view/#dom-element-scrollintoview) says (in step 6) that as long as the element has a layout object, we scroll it into view. The problem is that for content-visibility: hidden contents, we _may_ have a layout object or we may not, depending on whether rendering work as ever been done in that subtree. This means that the behavior of scrollIntoView is inconsistent. I propose that we call out scrollIntoView explicitly in content-visibility section under hidden and say that calling scrollIntoView on content-visibility: hidden subtrees has no effect (or something similar) /cc @tabatkins @frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6529 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 19 August 2021 19:47:36 UTC