- From: litherum via GitHub <sysbot+gh@w3.org>
- Date: Thu, 07 Jul 2016 16:03:55 +0000
- To: public-css-archive@w3.org
The implementation of this comparison function is site-specific, and therefore cannot be implemented by the browser. For example, the browser doesn't know th example to questions like these: - Many browsers don't implement font-stretch. Should this be a part of the comparison function? What happens when these browsers start implementing it? Existing websites break? - Should two URLs with different fragment identifiers be considered distinct? - What about "url(foo.woff)" compared with "url(foo.woff), url(fallback.woff)". These appear to be the same only if all the characters in the elements styled with them are supported by foo.woff - foo.woff and foo.woff2 are often conceptually same font - Are url(foo.ttf) and local(foo) distinct? - How about unicode-range? If the ranges for the two fonts don't overlap? If they overlap by only one code point? -- GitHub Notification of comment by litherum Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/273#issuecomment-231125921 using your GitHub account
Received on Thursday, 7 July 2016 16:04:08 UTC