-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Anne's feedback re: Non-goals and alternative approaches #20
Anne's feedback re: Non-goals and alternative approaches #20
Comments
If user agent A has a lot of market share and uses algorithm 2 and user agent B has few market share and uses algorithm 5, sites might be inclined to only account for A if the cost of doing the normalization client-side is too high (or not of interest). Generally the web platform tries very hard not to have implementation-defined behavior and whenever we do it's usually a problem. |
Also, clarify non-goals to ensure that the expected output, while possibly altered by the font processing in a browser, is still expected to continue to be in a valid OpenType format. Fixes https://github.com/inexorabletash/font-table-access/issues/6.
Hi Anne, thanks again for your feedback. The non-goal you're referring to is meant to give browsers necessary flexibility in their font sanitizer systems and not to introduce possibly non-standard table data formats. While we can't specify the font sanitizer algorithms in use by different browsers, we can make it clear that the output of the font table access APIs itself is expected to be in a valid OpenType format. I've posted inexorabletash/font-table-access#10 to make these changes. I'd like to hear if this change addresses your concerns, either in part or in whole. Feel free to post comments on the PR directly if you have suggestions. Thanks! |
I don't think anything apart from canonicalized/normalized addresses the concern expressed above. |
Also, clarify non-goals to ensure that the expected output, while possibly altered by the font processing in a browser, is still expected to continue to be in a valid OpenType format. Fixes https://github.com/inexorabletash/font-table-access/issues/6.
Also, clarify non-goals to ensure that the expected output, while possibly altered by the font processing in a browser, is still expected to continue to be in a valid OpenType format. Fixes https://github.com/inexorabletash/font-table-access/issues/6.
@annevk writes at w3ctag/design-reviews#400 (comment):
Hi Anne, thank you very much for your feedback! I'd like to understand it better.
Can you please clarify which of the explainer's non-goals you're referring to and why that is likely to introduce problems?
The text was updated successfully, but these errors were encountered: