- From: Luuk Lamers via GitHub <sysbot+gh@w3.org>
- Date: Mon, 06 May 2024 14:38:52 +0000
- To: public-css-archive@w3.org
@chrisarmstrong > When I say `background: black`, then switch it to `background: linear-gradient(45deg, black, white)`, it doesn't matter to me HOW the browser is implementing that instruction... I’m simply telling it what I want it to look like. If the browser has to switch to an entirely different rendering approach to implement that instruction in a performant way, that’s a problem for the browser dev, not the CSS dev. With that example, you're actually advocating for `display: masonry`. You change the value to make it do something different (rendering a color vs rendering a gradient). I've adopted your paragraph and inserted grid and masonry into it: When I say `display: block`, then switch it to `display: none`, or `display: grid`, or `display: masonry`, it doesn't matter to me HOW the browser is implementing that instruction... I'm simply telling it what I want it to look like. If the browser has to switch to entirely different rendering approach to implement that instruction in a performant way, that’s a problem for the browser dev, not the CSS dev. -- GitHub Notification of comment by xaddict Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-2096194903 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 6 May 2024 14:38:53 UTC