Icon for Pinned ProcessWire.com-Tab

[AndZyk]

Hey,

I know this is not a request for ProcessWire itself and you probably got better things to do, but since the release of Safari 9.0 I started to like the new pinned tabs feature.

As I am interested in all new things related to ProcessWire, I always got an tab open for your site as my starting point for new interesting topics.

One thing I would like, is when I pin your site to see a neat little icon. So could you please implement that? It would only just take a couple of minutes.

Regards, Andreas

[diogo]

I don't get it, why don't they use the favicon? Sometimes apple is just too bossy!

[AndZyk]

Maybe they wan't to be sure, that those icons will have transparency or maybe they plan to use those icons for something other than just pinning tabs.

But right now you're right. Apple often wants some special treatment. 

[LostKobrakai]

I don't get it, why don't they use the favicon? Sometimes apple is just too bossy!

You mean those 16x16 blobs of random pixels? It's indeed shitty, that they require own files for each damn iconsize they use, but not using favicons I can understand.

[diogo]

You mean those 16x16 blobs of random pixels? It's indeed shitty, that they require own files for each damn iconsize they use, but not using favicons I can understand.

They don't have to be that size, safari could check if the favicon has enough quality to be shown, and show it only then. Just  please don't force us to prepare more unnecessary files and add more tags to our code...

Edit: @AndZyk, I do agree with you that we should add this to the PW site, that's not the question here 

[adrian]

Why aren't all browsers (and Android/iOS apps) supporting SVG icons ?

Looks like Firefox already does and Safari is heading that way:

http://caniuse.com/#feat=link-icon-svg

Maybe the others will follow and all this icon sizing mess can be a thing of the past!

EDIT: Some discussion regarding SVG icons in chromium: https://code.google.com/p/chromium/issues/detail?id=294179

[teppo]

Just  please don't force us to prepare more unnecessary files and add more tags to our code...

They probably just thought that "hey, this fav/app icon/metadata stuff is a mess anyway, so where's the harm in adding one more to the list"

<link rel="apple-touch-icon" sizes="57x57" href="/apple-touch-icon-57x57.png">
<link rel="apple-touch-icon" sizes="60x60" href="/apple-touch-icon-60x60.png">
<link rel="apple-touch-icon" sizes="72x72" href="/apple-touch-icon-72x72.png">
<link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png">
<link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png">
<link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-120x120.png">
<link rel="apple-touch-icon" sizes="144x144" href="/apple-touch-icon-144x144.png">
<link rel="apple-touch-icon" sizes="152x152" href="/apple-touch-icon-152x152.png">
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon-180x180.png">
<link rel="icon" type="image/png" href="/favicon-32x32.png" sizes="32x32">
<link rel="icon" type="image/png" href="/android-chrome-192x192.png" sizes="192x192">
<link rel="icon" type="image/png" href="/favicon-96x96.png" sizes="96x96">
<link rel="icon" type="image/png" href="/favicon-16x16.png" sizes="16x16">
<link rel="manifest" href="/manifest.json">
<link rel="mask-icon" href="/safari-pinned-tab.svg" color="#5bbad5">
<meta name="msapplication-TileColor" content="#da532c">
<meta name="msapplication-TileImage" content="/mstile-144x144.png">
<meta name="theme-color" content="#ffffff">

.. and yeah, the current situation is a joke, really. Everyone is just adding their own metadata requirements, because hey, everyone else is doing it too and, perhaps, partly because of some messed up "we're so special we can't use what others use" mentality.

If only this was the one place where this is happening, but of course not. What about something like the Open Graph metadata?

Great idea, except that every service implements it in different way, and then along comes Twitter who decides that they're way too special to use what others use, and require their own twitter-metadata in addition to a half-assed support for Open Graph.

Sorry for the (mainly off-topic) rant, by the way

[Martijn Geerts]

perfectly valid HTML5:

<!DOCTYPE html>
<title>pw</title>
<p>

Time to drop your <head> ?

[diogo]

I will adopt that