mmcc
commented
10 years ago Even though our font is pretty tiny as far as icon fonts go, I still don't think the ~30% additional overhead for the base64 encoding is worth the tradeoff. If you're goal is to use Video.js locally, then it makes way more sense to use a local font as well.
@font-face{
font-family: 'VideoJS';
src: url('local/path/to/font/vjs.eot');
src: url('local/path/to/font/vjs.eot?#iefix') format('embedded-opentype'),
url('local/path/to/font/vjs.woff') format('woff'),
url('local/path/to/font/vjs.ttf') format('truetype'),
url('local/path/to/font/vjs.svg#icomoon') format('svg');
font-weight: normal;
font-style: normal;
}That is quite strange that it works off the DVD, though. ¯_(ツ)_/¯
Edit: Markdown is not very friendly to that emoticon.
gkatsev
sethborg
Video uses a font for the control bar icons and if you use the player locally off the hard drive Firefox blocks the font from loading due to its cross site scripting security http://red-team-design.com/firefox-doesnt-allow-cross-domain-fonts-by-default/ However, it works if played locally off a DVD. Is Firefox just treating the DVD as not local so things work better or is this a videojs bug?
Any thoughts on how to get around Firefox's local cross site scripting security for videojs's control bar font? Is it as simple as adjusting the CSS somehow with the local path?
Edit, videojs people, have you thought about embedding the font as a base64 string in your CSS to fix this issue?