- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 01 Oct 2018 18:47:22 +0000
- To: public-css-archive@w3.org
Current behavior of the testcase:
## Chrome
```
log: .foo { --foo:foo�; }
log: .foo { --foo:foo �; }
log: .foo { --foo:"foo"; }
```
## Safari
```
log: .foo { --foo: foo�; }
log: .foo { --foo: foo �; }
log: .foo { --foo: "foo"; }
```
## Firefox
```
log: .foo { --foo:foo\�; }
log: .foo { --foo:foo \�; }
log: .foo { --foo:"foo"; }
```
## Edge
```
log: .foo { --foo:foo\; }
log: .foo { --foo:foo \; }
log: .foo { --foo:“foo\; }
```
(Yes, Edge *really* printed these, every single one of which isn't even *remotely* correct.)
----
So, Edge is clearly super-wrong. Chrome and Safari agree, and obey the old resolution. (How they did so, when the spec doesn't say to do that, I'm not sure...) Firefox obeys the resolution, but unnecessarily escapes the U+FFFD when serializing.
Darn, I was hoping *somebody* implemented the thing I already had specced, so I didn't have to change anything. ^_^
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3182#issuecomment-426019418 using your GitHub account
Received on Monday, 1 October 2018 18:47:23 UTC