- From: Luis Pato via GitHub <sysbot+gh@w3.org>
- Date: Fri, 18 Oct 2024 06:04:29 +0000
- To: public-css-archive@w3.org
@mirisuzanne I am not really sure what causes the differences, so i can't explain them very well. I can only describe what i saw... On Chrome v129 everything seemed to work fine, but on Chrome v128 we couldn't scroll. Also on Firefox or Safari we couldn't scroll! Yes, i have seen you article. It was actually what lead me to this gh issue. Thank you, i found your article really helpful! 🤗 I have also tested the solution you have at the end of your article. But i ended update having some problems with fixed elements overlapping the scrollbar, something like this:  In the end i did actually use something very similar to what you suggest here on your comment. i turned the main, footer, ... into containers. But, tbh, i think the best would be to just turn the elements themselves into container. The problem with that is that each element needs an extra "container wrapper", so the element can be the container, and the wrapper can listen to the parent @container -- GitHub Notification of comment by luis-pato Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9003#issuecomment-2421503158 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 18 October 2024 06:04:30 UTC