- From: Stephen Chenney via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Feb 2024 14:15:52 +0000
- To: public-css-archive@w3.org
Inheriting through both originating ancestors and highlight ancestors is possible to implement, I think. On the other hand, I'm reconsidering this proposal anyway because of the memory costs of inheriting so much stuff, plus the potential confusion of where properties are coming from (DevTools support would need to change in Chrome, for instance). And making the changes either of us suggest does not fix all website breakage. There's no way of getting around sites that have a foo::selection that they only expect to apply to foo, and not its decendents. I'll ponder this some more and maybe try to figure out how much stuff is broken due to which aspect of the change: custom properties and/or unexpected inheritance. -- GitHub Notification of comment by schenney-chromium Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9909#issuecomment-1948462174 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 16 February 2024 14:15:54 UTC