- From: Steinar H. Gunderson via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Oct 2022 17:06:19 +0000
- To: public-css-archive@w3.org
> How difficult/expensive would it be to _change it_ to do so? The best numbers I have is that it would cost us about 2% of total page load time (not just parse time; all of load time), since we'd need to remove some optimizations that have been said to yield approximately that. > So far we have been designing syntax around it, accepting it cannot possibly be solved in a performant way as an axiom. I'd like us to challenge that assumption, and for that we need more details from implementers than "NAK". I don't share this goal; I would like us to just get the syntax (_any_ syntax) specified, out the door and be done with it. So no, I won't be spending resources trying to bend our minds around how we tokenize CSS to this avail; I can NAK what is a non-starter for us, and that's what you'll get. -- GitHub Notification of comment by sesse Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7961#issuecomment-1293823165 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 October 2022 17:06:20 UTC