Skip to content
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

Chrome CORS issue on https://assets.mozilla.net/fonts/FirefoxSharpSans-Medium.woff2 #1118

Closed
jgmize opened this issue May 28, 2019 · 3 comments

Comments

3 participants
@jgmize
Copy link
Member

commented May 28, 2019

@metadave

This comment has been minimized.

Copy link
Member

commented May 29, 2019

@craigcook what project is this related to?

@jgmize jgmize added this to Queued (2 weeks) in MozMEAO backend/infra May 30, 2019

@craigcook

This comment has been minimized.

Copy link

commented May 31, 2019

@craigcook what project is this related to?

It was originally related to the redesigned accounts page, but I subsequently removed the font from that page because it will be formally arriving with the next version of Protocol any day now (see mozilla/bedrock#7227).

I don't know if this will still be relevant but suspect it might be... I'm looking at https://bedrock-demo-protocol.oregon-b.moz.works in Chrome and seeing no CORS errors, BUT I'm also not seeing any pages using Sharp Sans Medium (which is what triggered the issue), only Bold (which didn't). So this may still warrant further investigation and testing in case it manifests again.

@jgmize jgmize changed the title Workaround chrome CORS issue on assets.mozilla.net Workaround chrome CORS issue on https://assets.mozilla.net/fonts/FirefoxSharpSans-Medium.woff2 Jun 3, 2019

@jgmize jgmize changed the title Workaround chrome CORS issue on https://assets.mozilla.net/fonts/FirefoxSharpSans-Medium.woff2 Chrome CORS issue on https://assets.mozilla.net/fonts/FirefoxSharpSans-Medium.woff2 Jun 3, 2019

@jgmize

This comment has been minimized.

Copy link
Member Author

commented Jun 3, 2019

This issue currently blocks mozilla/bedrock#7227, but I'm not going to prioritize implementing workarounds for this incompatibility with our existing open source software, deployment, and build systems, because that would mean saying no to other priorities. Instead, I'm going to say no to this font. While I'm sure the original decision to move forward with this font was made with best intentions, this is ultimately an engineering decision, and I believe it is fundamentally at odds with our open source values and with the Mozilla mission. I am opposed to including "Firefox Sharp Sans" or any other proprietary font in our websites or in our products.

@jgmize jgmize closed this Jun 3, 2019

MozMEAO backend/infra automation moved this from Queued (2 weeks) to Complete Jun 3, 2019

@metadave metadave moved this from Complete to Review in MozMEAO backend/infra Jun 4, 2019

@metadave metadave moved this from Review to Complete in MozMEAO backend/infra Jun 28, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.