nekobus
/
mastodon_neko
forked from closed-social/mastodon
1
0
Fork 0
Code Issues 0 Pull Requests 0 Projects 0 Releases 0 Wiki Activity
闭社主体 forked from https://github.com/tootsuite/mastodon
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2661 Commits
2 Branches
112 MiB
Tree: 302c0d2046
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '302c0d2046'
${ noResults }
mastodon_neko/app/assets/stylesheets/fonts/roboto-mono.scss

12 lines
595 B
Raw Normal View History

Move the fonts from Google Fonts to local assets Currently we have two problems that are resolved by this change. The first is that we have a dependency on Google Fonts, which means that should it ever go down, or it have issues we would also have issues. This will resolve this by moving the dependencies we load from there to the local server. The second issue is that Google Fonts is currently returning the `local()` css font source. This causes a problem where the users browser fails to fallback to a missing glyph, resulting in many unusual characters displaying the failure glyph. This will resolve this by creating a font-family definition that does not use the `local()` source. I did not update the error pages with local fonts, they still use the remote google fonts api, so they're a self contained page that does not use the asset pipeline. This resolves tootsuite/mastodon#531 and tootsuite/mastodon#12
7 years ago
​
Use local fonts and stop scrollable elements from repainting (#2266)
7 years ago
Move the fonts from Google Fonts to local assets Currently we have two problems that are resolved by this change. The first is that we have a dependency on Google Fonts, which means that should it ever go down, or it have issues we would also have issues. This will resolve this by moving the dependencies we load from there to the local server. The second issue is that Google Fonts is currently returning the `local()` css font source. This causes a problem where the users browser fails to fallback to a missing glyph, resulting in many unusual characters displaying the failure glyph. This will resolve this by creating a font-family definition that does not use the `local()` source. I did not update the error pages with local fonts, they still use the remote google fonts api, so they're a self contained page that does not use the asset pipeline. This resolves tootsuite/mastodon#531 and tootsuite/mastodon#12
7 years ago
​
​
​
​
​
​
​
​
 
  1. @font-face {
  2.   font-family: 'Roboto Mono';
  3.   src: local('Roboto Mono');
  4.   src: font-url('roboto-mono/robotomono-regular-webfont.eot');
  5.   src: font-url('roboto-mono/robotomono-regular-webfont.eot?#iefix') format('embedded-opentype'),
  6.   font-url('roboto-mono/robotomono-regular-webfont.woff2') format('woff2'),
  7.   font-url('roboto-mono/robotomono-regular-webfont.woff') format('woff'),
  8.   font-url('roboto-mono/robotomono-regular-webfont.ttf') format('truetype'),
  9.   font-url('roboto-mono/robotomono-regular-webfont.svg#roboto_monoregular') format('svg');
  10.   font-weight: 400;
  11.   font-style: normal;
  12. }