- From: Xidorn Quan via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Mar 2017 07:05:05 +0000
- To: public-css-archive@w3.org
upsuper has just created a new issue for https://github.com/w3c/csswg-drafts: == [cssom] Serialization of NULL in string == The [algorithm to serialize a string](https://drafts.csswg.org/cssom/#serialize-a-string) has a separate clause for NULL character which says: > If the character is NULL (U+0000), then the REPLACEMENT CHARACTER (U+FFFD) escaped as code point. However, this doesn't match behavior of any browser. Firefox and Chrome serialize NULL character to U+FFFD without escaping it as code point. Edge strips anything after NULL, and Safari serializes it as the character escaped as code point (so `\0`). I guess the spec means to do what Firefox and Chrome are currently doing, so probably we should fix the spec text? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1105 using your GitHub account
Received on Thursday, 16 March 2017 07:05:12 UTC