Re: [csswg-drafts] [css-syntax] Urange and its problems (#3588)

@SimonSapin @emilio Firefox fails almost all of these tests, because in every single case (including the invalid ones!) it just returns exactly what the author wrote into `unicode-range`. That seems like broken behavior in the first place, and it also makes this much harder to test. Any insight into why this is?

-- 
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3588#issuecomment-459900116 using your GitHub account

Received on Friday, 1 February 2019 23:13:44 UTC