- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Jun 2023 06:26:23 +0000
- To: public-css-archive@w3.org
Searching WPT with a regexp might surface some cases but not nearly everything. The issues are incorrect calculations, not incorrect syntax. Some of these test files contain hundreds of individual cases. My approach to listing issues in WPT would be : - take any test case - take any browser - compare with `color.js` - compare with `postcss-preset-env` If the outcome differs between the browser implementation and the static tools I would re-read the relevant specification sections in search of which step was likely implemented incorrectly. But this is a painfully slow process and prone to errors. ------ I suspect it is more efficient if an implementer volunteers and reviews recent specification changes and open issues tagged with css-color-4 and css-color-5. This is still a lot of work, but the outcome will be better I think. -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8943#issuecomment-1610828776 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 28 June 2023 06:26:25 UTC