Skip to main content

Home/ Web Development, Design & Programming/ Group items tagged webkit

Rss Feed Group items tagged

Vernon Fowler

@font-face gotchas « Paul Irish - 1 views

  • 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.
  •  
    "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. "
Vernon Fowler

The future of CSS layouts | Feature | .net magazine - 1 views

  •  
    "Conclusion FlexBox and Columns aside, it's still not definite which new layout modules will be fully implemented cross-browser. I'd say that Positioned Floats and Exclusions are very similar, and could easily be merged (indeed, this seems to be happening). Grid Layout has subsumed Template Layout, and will definitely be in IE10. Regions has already been implemented in a fork of WebKit, so could appear in WebKit browsers (Safari, Chrome, etc) very quickly. So I'd be willing to predict that with some changes to syntax, most of what you see here will make it into CSS3 in the future. If that's the case, I think it's a good thing; these new methods are complementary, not competing, and with a minimum of work will allow us to build very sophisticated websites a few years from now."
Vernon Fowler

WebKit HTML5 Search Inputs | CSS-Tricks - 2 views

  • This isn't documented anywhere that I know of nor is it in the spec, but you if you add a results parameter on the input, WebKit will apply a little magnifying glass with a dropdown arrow showing previous results.
Jochen Burkhard

Quick Tip: Pure CSS Text Gradients | Nettuts+ - 0 views

  •  
    With the latest advancements in CSS, we now have access to powerful styling techniques, including box shadows, rounded corners, background gradients, etc. However, we don't currently have the ability to apply gradients to the text itself. Luckily, with a bit of trickery, we can force this effect - at least in webkit browsers! I'll show you how in today's video quick tip.
tom studer

Jeffrey Zeldman - The Medium Comes of Age on Vimeo - 0 views

shared by tom studer on 24 Aug 11 - No Cached
  •  
    Jeffrey Zeldman's keynote talk from DIBI Conference 2011. Webkit-powered smartphones like iPhone and Droid have come along at precisely the moment when HTML5, CSS3, and web fonts are ready for action; when standards-based web development is no longer relegated to the fringe; and when web designers, no longer content to merely decorate screens, are crafting provocative, multi-platform experiences powered by research, strategy, and years of social media know-how. Study the thinking and inventions that led to the web, and learn why this is a *great* time to be a web designer, creating a mature, ubiquitous web powered by standards.
awqi zar

Mobile Boilerplate - 0 views

  •  
    Mobile Boilerplate is your trusted template made custom for creating rich and performant mobile web apps. You get cross-browser consistency among A-grade smartphones, and fallback support for legacy Blackberry, Symbian, and IE Mobile. Mobile Boilerplate is not a framework, but works well with projects like jQuery Mobile, Sencha Touch, Phonegap and Appcelerator. You get an offline caching setup for free, fast button clicks, a media query polyfill, and many common mobile WebKit optimizations waiting for you. Use Mobile Boilerplate to start your mobile webapp quickly and immediately benefit from community best practices.
1 - 11 of 11
Showing 20 items per page