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
Whitelist Typography.com fonts #3749
Comments
Absolutely possible. Steps:
@arajay Are you with typography.com? |
I do not work for typography.com but many of my clients use their CDN hosted fonts; in the meantime I have been using alternate web-safe fonts for my AMP pages instead. |
Do you know what the range of possible URLs here would be? |
Affirmative @Gregable ; the stylesheet links for all my clients are formatted in that manner. |
@arajay Could you try to get somebody from typography.com to comment here. Many font providers do referrer checking which may require additional work for AMP. |
"Sarah," a representative from Typography.com replied to my request with: "We do not allow for the white listing of domains." |
I'm not sure what that means :) So, lets go ahead here. @Gregable I think just going for the prefix |
Closing, but will be a little while longer before it's released. |
I assume we still need to make the CSP change, right? Sending you a CL. |
New CSP
|
This is now live everywhere. |
* Allow skype as a protocol for anchor tag's href. ampproject#4094 * Whitelist typography.com fonts ampproject#3749
Typography.com is a custom font provider. Their basic licensing agreement prohibits the download of their custom fonts; the only option for font embedding (without paying a hefty licensing fee) is to link to their cloud hosted stylesheet.
Example:
<link rel="stylesheet" type="text/css" href="//cloud.typography.com/6256354/724768/css/fonts.css">
This is a request to whitelist Typography.com CDN for serving fonts to AMP clients.
Is this possible? Or would it require each individual stylesheet URL to be whitelisted in the AMP CSP, as indicated by the response to this request?
The text was updated successfully, but these errors were encountered: