- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 Oct 2019 12:41:51 +0000
- To: public-css-archive@w3.org
@lorp thanks for raising this, and for the detailed and clear write-up. @litherum it would be interesting to hear the WebKit perspective on this. Was this simply an oversight, so it should be treated as a spec-compliance browser bug, or was this a deliberate decision and if so, what was the rationale? -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4430#issuecomment-543155929 using your GitHub account
Received on Thursday, 17 October 2019 12:41:53 UTC