woff2

Font rendering in Chrome (woff2) - after load font family doesn't want to change

由 房东的猫 提交于 2019-12-11 13:09:03
问题 To prevent font rendering lags related to font loading time I wrote some simple script which load CSS containing @font-face and custom fonts with some delay. Thanks to that solution, by default system fonts are used (no lag) and later they are overwrite by new CSS with new fonts. However, solution works everywhere except Chrome. In chrome network tab I can see that fonts were loaded but somehow they were not re-rendered. How it looks in IE, and Firefox (desired fonts): And Chrome (system

CORS Issue with woff2 fonts behind CDN in Chrome

由 雨燕双飞 提交于 2019-12-06 11:23:17
问题 I have an S3 Bucket fronted with a Cloudfront CDN. In that bucket, I have some woff2 fonts that were automatically tagged with the content type octet-stream . When trying to load that font from a CSS file on a live production website, I get the following error: Access to Font at 'https://cdn.example.com/fonts/my-font.woff2' from origin 'https://www.live-website.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https:/

CORS Issue with woff2 fonts behind CDN in Chrome

由 故事扮演 提交于 2019-12-04 17:07:37
I have an S3 Bucket fronted with a Cloudfront CDN. In that bucket, I have some woff2 fonts that were automatically tagged with the content type octet-stream . When trying to load that font from a CSS file on a live production website, I get the following error: Access to Font at 'https://cdn.example.com/fonts/my-font.woff2' from origin 'https://www.live-website.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://www.live-website.com' is therefore not allowed access. The thing is that a curl reveals that the Access

Font Face isn't working in IIS 8.0

由 和自甴很熟 提交于 2019-11-29 20:13:02
I have a font-face in my program generated from Font Squirrel I just can't get it to work in IIS, it works in localhost. I added application/font-woff article to my MIME Types but it still doesn't want to work. Context --Fonts ----font location --css files CSS @font-face { font-family: 'wallStreetFont'; src: url('Fonts/subway-webfont.eot'); src: url('Fonts/subway-webfont.eot?#iefix') format('embedded-opentype'), url('Fonts/subway-webfont.woff2') format('woff2'), url('Fonts/subway-webfont.woff') format('woff'), url('Fonts/subway-webfont.ttf') format('truetype'); font-weight: normal; font-style:

Font Face isn't working in IIS 8.0

由 泪湿孤枕 提交于 2019-11-28 16:04:32
问题 I have a font-face in my program generated from Font Squirrel I just can't get it to work in IIS, it works in localhost. I added application/font-woff article to my MIME Types but it still doesn't want to work. Context --Fonts ----font location --css files CSS @font-face { font-family: 'wallStreetFont'; src: url('Fonts/subway-webfont.eot'); src: url('Fonts/subway-webfont.eot?#iefix') format('embedded-opentype'), url('Fonts/subway-webfont.woff2') format('woff2'), url('Fonts/subway-webfont.woff

Proper MIME type for .woff2 fonts

由 泄露秘密 提交于 2019-11-26 06:05:12
问题 Today I updated Font Awesome package to 4.3.0 and noticed that woff2 font was added. That file is linked in CSS so I need to configure nginx to serve woff2 files properly. Currently I have this block in nginx config for fonts: location ~* \\.(otf|eot|woff|ttf)$ { types {font/opentype otf;} types {application/vnd.ms-fontobject eot;} types {font/truetype ttf;} types {application/font-woff woff;} } What is proper mime type for woff2 fonts? 回答1: In IIS you can declare the mime type for WOFF2 font

Are eot, ttf, and svg still necessary in the font-face declaration?

由 萝らか妹 提交于 2019-11-26 00:43:57
问题 Up until now, I\'ve used Paul Irish\'s bulletproof font-face syntax But I was just looking at support for .woff and .woff2 files on caniuse and it says woff is supported in IE9+. Most articles on this topic are from around 2009, which at the time of this writing was a full 7 years ago. Do we really need to keep declaring ttf, otf, eot, and svg when woff now enjoys such wide support? 回答1: October 2018 edit tl;dr: only use WOFF2, every still-supported browser supports it, the end. Original
订阅 woff2