- From: Westbrook Johnson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Jul 2024 15:48:59 +0000
- To: public-css-archive@w3.org
I'm running into a _similar_ issue with regards to "absolutely positioned" content. See [this](https://codepen.io/Westbrook/pen/wvLBwLP) broken example wherein: - the parent element is `position: fixed;` - the anchor element is `position: fixed;`, and - the content element is `position: fixed;` AND on the `#top-layer` Leading to the content not being positioned relative to the anchor: ![within fixed positioned ancestor](https://github.com/w3c/csswg-drafts/assets/1156657/506d0145-ac93-484b-a898-8440f22748cd) You can work around this by positioning the parent differently, as seen [here](https://codepen.io/Westbrook/pen/QWXwWWx): - the parent element fills the screen with `width` and `height` - the anchor element is `position: fixed;`, and - the content element is `position: fixed;` AND on the `#top-layer` Leading to the content being positioned as expected: ![within sized ancestor](https://github.com/w3c/csswg-drafts/assets/1156657/1b04eb3d-4b5b-4949-8909-bcce293ca41b) Do we see this as "outside of the spec", something yet to be covered, an implementation issue? I've opened a [Chromium bug](https://issues.chromium.org/issues/352005194) in case it is the later... -- GitHub Notification of comment by Westbrook Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10419#issuecomment-2220886396 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 10 July 2024 15:48:59 UTC