Skip to main content

Home/ Web Development, Design & Programming/ Group items tagged snook-style

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Raja uk

Snook-Style Navigation Using MooTools | Ajaxmint.com - 0 views

ajaxmint.com/...tyle-navigation-using-mootools

snook-style mootools

shared by Raja uk on 11 Jan 10 - No Cached
  • Raja uk on 11 Jan 10
     
    Tutorial to Create Snook-Style Navigation Using MooTools
Vernon Fowler

@font-face gotchas « Paul Irish - 1 views

paulirish.com/...font-face-gotchas

@font-face css3 typography font-face fonts css webdesign web design

shared by Vernon Fowler on 10 Oct 12 - No Cached
  • There are a few reasons why smiley is a better solution: Webkit+Font Management software can mess up local references, like turning glyphs into A blocks.  (crbug.com/33173) On OS X, Font Management software may alter system settings to show a dialog when trying to access a local() font that's accessible outside of Library/Fonts. More detail on my bulletproof post. (crbug.com/29729) Font Explorer X is also known to mess up other stuff in Firefox: bugzil.la/531771 Although it's unlikely, you could reference a local() font which is completely different than what you think it is. (Typophile post on different fonts, same name) At the very least its a risk, and you're ceding control of the type to both the browser and host machine. This risk may not be worth the benefit of avoiding the font download. These are all pretty edge case issues, but it's worth considering. FontSquirrel has already made the smiley syntax the new default in the Generator, and you should use it going forward as well.
  • And.. regarding @font-face syntax I now recommend the bulletproof smiley variation over the original bulletproof syntax.
  • @font-face { font-family: 'Graublau Web'; src: url('GraublauWeb.eot'); src: local('?'), url('GraublauWeb.woff') format('woff'), url('GraublauWeb.ttf') format('truetype'); }
  • ...5 more annotations...
  • in Webkit (Chrome/Safari), applying font-weight:bold to faux-bold some @font-face'd text will not succeed. Same applies for font-style:italic.
  • text-transform doesn't play well with @font-face in current implementations.
  • @font-face doesnt play nice with css transitions.
  • If a @font-face declaration is within a media query @media screen { ..., it will fail in Firefox.
  • SVG Fonts - Currently SVG is the only way to get webfonts working on iPhone and iPad.
  • Vernon Fowler on 10 Oct 12
     
    "There are a few reasons why smiley is a better solution: Webkit+Font Management software can mess up local references, like turning glyphs into A blocks.  (crbug.com/33173) On OS X, Font Management software may alter system settings to show a dialog when trying to access a local() font that's accessible outside of Library/Fonts. More detail on my bulletproof post. (crbug.com/29729) Font Explorer X is also known to mess up other stuff in Firefox: bugzil.la/531771 Although it's unlikely, you could reference a local() font which is completely different than what you think it is. (Typophile post on different fonts, same name) At the very least its a risk, and you're ceding control of the type to both the browser and host machine. This risk may not be worth the benefit of avoiding the font download. These are all pretty edge case issues, but it's worth considering. FontSquirrel has already made the smiley syntax the new default in the Generator, and you should use it going forward as well. "
1 - 2 of 2
Showing 20▼ items per page