- From: John Mellor <johnme@google.com>
- Date: Mon, 28 Jul 2014 15:59:16 +0100
- To: Mathias Bynens <mathiasb@opera.com>
- Cc: WHATWG <whatwg@whatwg.org>
Chrome 30 dropped support[1] for fetching apple-touch-icon-* from well known URLs, since the 404 pages that are usually returned were consuming 3-4% of all mobile bandwidth usage[2]. We're unlikely to reverse that. We still support apple-touch-icon-* via link rel under some circumstances (e.g. for add to homescreen), but they're deprecated[3], since we'd like authors to use the standard for this, i.e.: <link rel="shortcut icon" sizes="128x128" href="/favicon.png"> (or even good old: <link rel="shortcut icon" href="/favicon.ico"> with multiple resolutions in the .ico file for compatibility with IE<11). [1]: https://code.google.com/p/chromium/issues/detail?id=259681 [2]: https://bugs.webkit.org/show_bug.cgi?id=104585 [3]: https://code.google.com/p/chromium/issues/detail?id=296962 On 28 July 2014 08:35, Mathias Bynens <mathiasb@opera.com> wrote: > On Sun, Jul 27, 2014 at 1:13 PM, Anne van Kesteren <annevk@annevk.nl> > wrote: > > For <link rel=icon> we already define the /favicon.ico fallback. If a > > page lacks <link rel=icon sizes> we should probably also look at > > Apple's proprietary extension here given that it's quite widely > > adopted. Chrome supports it and there is some work going on in Firefox > > as well: https://bugzilla.mozilla.org/show_bug.cgi?id=921014 > > FWIW, Chrome’s intention was to drop support for Apple’s magic file > names at some point. > https://developer.chrome.com/multidevice/android/installtohomescreen#icon > But I agree — it seems that this won’t happen any time soon. > > In case it helps, here’s some more info on touch icon support on > various OS/devices: http://mathiasbynens.be/notes/touch-icons >
Received on Monday, 28 July 2014 14:59:56 UTC