You may want these for a presentation, a, blog post or for the site featuring your brand new awesome lightbox script (please no!). They are 32bit PNGs, each have their own official shadow treatment, and no background matte color.
Includes much more than the standard five browsers.
2011.04.13: new chrome, chromium and IE9 logos! (i’ll better integrate these later on maybe)
2011.05.19: Peter Lubbers of Kaazing has put all the updated logos together and has all sizes, both individual and group imagery. Also run through OPTIpng! Awesome. http://paulirish.com/lovesyou/new-browser-logos/ ← 2012.02.03: Updated this post. 2012.11.06: Reorged all the files. Updated this post. Freshness. More high resolution goodness.
I’ve rerecorded my talk in screencast form. Here’s what to expect from the 52 minute video:
It’s jQuery on the big screen. We’ll open the jQuery source and run through how the jQuery object works, covering self-executing anonymous functions as a global abatement technique, several interesting jQuery methods, internal jQuery paradigms, and hiddenhancements. You’ll learn JavaScript techniques you can apply to your own code, as well as the basic workings of jQuery itself.
Enjoy. Please comment if you have a question or if I messed something up. :)
Also, (you should already know this, but…) if you like this screencast you should subscribe to the yayQuery Podcast. It’s techy but entertaining and there will be smiles.
As you might have see, Google now offers a full webfont API. Luckily, they let me dig into the service and code a few weeks back. So let me give you the lowdown on the features and what you can do with it…
Here’s adding a @font-face declaration for Tangerine, a nice scripty font:
Obviously there are huge caching benefits to using the Google Font API, plus they’re very focused on performance and you can expect things to be fast and FOUT to be minimized. But on the topic of FOUT…
The WebFont Loader is also making its debut. This is a javascript library collaboration between the good boys at Typekit and Google. It basically allows a lot of control over the display details of webfonts.
Let’s say you want Firefox to not have the FOUT, but rather mimic webkit’s behavior of invisible text until the font is loaded:
Ask any questions in the comments and I’ll do my best to clarify. :)
2010.05.19: The Google webfont previewer tool (with jQuery!) is pretty tight, too.
2010.05.20: Update via Florian to use .wf-loading to hide for FOUT prevention.
Take a look at some of my other (recently updated) webfont stuff: