Closed rocc-o closed 2 years ago
unicode-range: U+20-22,U+26-2A,U+2C-3B,U+3F-5A,U+61-7A,U+A9,U+E8,U+E9,U+2014,U+2018,U+2019,U+201C,U+201D;
works well in the CSS Validator (see https://jigsaw.w3.org/css-validator/#validate_by_input ), so it may be that the nu HTML Checker might not be up-to-date. I suggest filing an issue there. (pinging @sideshowbarker )
Sorry, my bad, I confused them with each other. I have now bookmarked https://jigsaw.w3.org/css-validator/ Thanks!
Thanks much for reporting this. I’ve pushed an update to https://validator.w3.org/nu/, so I believe this should now be working as expected there too.
Hello, sorry to bother, but this issue is still happening whenever I put
unicode-range: U+20-22,U+26-2A,U+2C-3B,U+3F-5A,U+61-7A,U+A9,U+E8,U+E9,U+2014,U+2018,U+2019,U+201C,U+201D
for fonts subsettings, and it seems to be a bug in the validator. I'm missing something, or there's a way to solve this? Thanks!