- From: danegraphics via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 Jun 2018 17:31:59 +0000
- To: public-css-archive@w3.org
> A custom-written script solving someone's specific needs, on the other hand, often doesn't need to worry about all of that, and can ignore a lot of sanity-checking and edge-cases that CSS has to worry about. OOOoookay, that makes a lot of sense! Thanks for clearing that up! > The issue, tho, is that if we build it in, people will use it more. Ah... I see. You wish to avoid _abuse_ of the feature. It isn't simply that it's a _performance_ problem, it's that it's a performance problem that would likely end up _widespread_. So while a feature may work well at accomplishing many tasks that other CSS can't accomplish on its own, the feature may actually be so flexible that people will use it where it isn't necessary (where other CSS or html structure is possible to accomplish the same task), and end up taking a performance hit because of it. Is that what you mean? -- GitHub Notification of comment by danegraphics Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2731#issuecomment-393952576 using your GitHub account
Received on Friday, 1 June 2018 17:32:09 UTC