- From: Keith Cirkel via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Mar 2021 17:43:25 +0000
- To: public-css-archive@w3.org
I think you're right, it looks a lot like Step 3 of that algo: > 3. While container is not the intersection root: > 1. If container is the document of a nested browsing context, update intersectionRect by clipping to the viewport of the document, and update container to be the browsing context container of container. > 2. Map intersectionRect to the coordinate space of container. > 3. If container has overflow clipping or a css clip-path property, update intersectionRect by applying container’s clip. > 4. If container is the root element of a browsing context, update container to be the browsing context’s document; otherwise, update container to be the containing block of container. Perhaps this algo can be abstracted out into a method on an element? -- GitHub Notification of comment by keithamus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6132#issuecomment-806029285 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 March 2021 17:43:26 UTC