On Fri, Jul 25, 2014 at 5:37 AM, Alive <al...@mozilla.com> wrote: > https://bugzilla.mozilla.org/show_bug.cgi?id=921014 is tracking: > support link rel="apple-touch-icon” in our browser API. >
I dislike this a lot as it's equivalent to adopting Webkit prefixes in Gecko. However, the icons we get when we currently add bookmarks to the homescreen from the browser on Firefox OS and Android are of very poor quality which whether we like it or not can negatively effect the perception of the quality of our products. There's some work going on at the moment to improve this by better supporting multiple icons provided by web sites in the standard ways, by making use of the sizes attribute to link rel=icon and unpacking multiple icons from a single file. But if you look at the data [1] this probably isn't going to go far enough towards solving the problem. Whilst 288 of the Alexa Top 500 web sites support the standard rel="icon" attribute, only two use the sizes attribute and anecdotally most seem provide a low quality (often 16-32px) icon, although I'd like to see data on this. By comparison, 100 sites use proprietary apple attributes which tend to be higher quality icons. So if after the standards-based work is complete we still see poor quality icons in practice, I do think there's an argument (though one I dislike) to support apple-touch-icons on a temporary basis. Chrome supports the Apple proprietary attributes in their bookmark to homescreen feature on Android, but warn in their developer documentation that "The last two formats (apple-touch-*) are deprecated, and will be supported only for a short time." [2] If we go down this route I would like to see us add similar caveats and consider adding a warning to the developer console telling developers that they're using a deprecated proprietary feature which has a standards-based equivalent. (I have no idea how effective this has been in the past). It would also be great to speak with people at Apple and Google about a deprecation plan. Note that the W3C Manifest specification will also provide a future recommendation for how to provide icons for web apps [3] which seems to have a lot of cross-platform interest. But this specification explicitly falls back to link rel=icon when icons are not provided in the manifest so that doesn't change the need to improve support there. 1. https://bugzilla.mozilla.org/show_bug.cgi?id=921014#c19 1. https://developer.chrome.com/multidevice/android/installtohomescreen 2. http://w3c.github.io/manifest/#icons-member _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
