- From: Simon Sapin via GitHub <sysbot+gh@w3.org>
- Date: Thu, 06 Dec 2018 12:20:42 +0000
- To: public-css-archive@w3.org
> Perhaps this is just related to which definition each uses for CSSOMString? Yes, exactly. Firefox (since 57) treats string in CSSOM effectively as `USVString`. I proposed changing the CSSOM spec to use `USVString` in https://github.com/w3c/csswg-drafts/issues/1217, but other implementations were opposed. This is why we introduced `CSSOMString`: to allow each implementation to pick either. I’m a bit surprised that maintainers of Blink and EdgeHTML and WebKit have changed their mind since last year, but if they have I’m glad we can simplify the spec. @tabatkins When do this in the tokenizer algorithm rather than removing `CSSOMString` and using `USVString` in CSSOM? -- GitHub Notification of comment by SimonSapin Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3307#issuecomment-444853241 using your GitHub account
Received on Thursday, 6 December 2018 12:20:49 UTC