w3c / w3c/csswg-drafts

[css-contain-2] Consider forcing layout on content that is skipped when querying it on an element with content-visibility

Open
#9,675 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

css-contain-2
Dominant language
Bikeshed
Stars
4.9k
Forks
816
PR merge metrics
PR metrics pending

Description

On https://rishi.app/blog/using-dotenv-vault-with-edgio-and-nuxt-js/

$("ul").getBoundingClientRect() will return a zero height, but will return the correct height when scrolled into view. ul has content-visibility: auto so only its contents are skipped, so lazy layout doesn't apply here unfortunately.

It seems a bit unexpected, especially when the spec says values queried from script should be consistent.

cc @rwlbuis @vmpstr @smfr @nmoucht

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reproduction at the linked rishi.app page and the CSS Containment Level 2 issue discussion, focusing on content-visibility:auto and getBoundingClientRect(). Determine whether the specification should require layout for skipped content queried by script; done means the expected behavior and any corresponding spec change are agreed and recorded.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.