Month: July 2012

jQuery 2.0 will drop support for MSIE 6, 7, and 8

Slashdot reports:

The developers of jQuery recently announced in a blog entry that jQuery 2.0 will drop support for legacy versions of Internet Explorer. The release will come in parallel with version 1.9, however, which will include support for older versions of IE. The versions will offer full API compatibility, but 2.0 will ‘benefit from a faster implementation that doesn’t have to rely on legacy compatibility hacks.

A few comments mentioned that dropping support for MSIE 6 and 7 is fine, but MSIE 8 is still widely used by people with Windows XP.  The solution to the problem seems to be conditional tags.  Since jQuery 2.0 will have fully compatible APIs to jQuery 1.9, something along the lines of:


<!--[if lt IE 9]>
<script src="jquery-1.9.0.js"></script>
<![endif]-->
<!--[if gte IE 9]>
<script src="jquery-2.0.0.js"></script>
<!--<![endif]-->

should solve the problem.

Ultimate guide for CSS support in email clients

Ultimate guide for CSS support in email clients

Designing an HTML email that renders consistently across the major email clients can be very time consuming. Support for even simple CSS varies considerably between clients, and even different versions of the same client.

We’ve put together this guide to save you the time and frustration of figuring it out for yourself. With 24 different email clients tested, we cover all the popular applications across desktop, web and mobile email.

As the number of email clients continues to grow, we’ve decided to simplify the web-based version of the guide to focus on the 10 most popular email clients on the market. For the complete report on all 24 email clients across the desktop, web and mobile email world, download the complete guide in PDF format.

Linking to favicons

Favicons have been around for a few years now.  But they were mostly used by the browsers – in multi-tab environments and in bookmark managers.  Recently I’ve noticed the trend to use favicons in web design – next to external links or near the blog comment’s author, etc.

Adding a favicon to the design is a simple thing for the designer.  But a totally different story for the web developer.  Favicons can be either dropped into the root folder of the site or linked to from the page’s HTML.  On top of that, the times of the single favicon.ico format are long gone too.  These days you could get a GIF or PNG image.

So, how would reliably finda favicon of a site?  It turns out, you don’t really have to work too hard, since someone has already solved your problem.  From comments to this article (in Russian) I’ve learned of the Google web service.  So, all you’ll need to do is this (with whatever domain name that you need):

<img src="http://www.google.com/s2/favicons?domain=mamchenkov.net">

Works and sound good, right?  Wrong!  As I mentioned already, there is a way to link to favicons from HTML.  And this service doesn’t seem to take that into account.  Well, not to worry anyway.  There is another one that does – getFavicon.  This one works in a very similar way, but supports the full URL as a parameter.  For example:

<img src="http://g.etfv.co/https://mamchenkov.net/wordpress/">

On top of that, you can include properly encoded GET parameters, and avoid browser’s per-server connection limit, by using multiple sub-domains.  Brilliant, I say.