selbekk / app-favicon Goto Github PK

I don't know much about the details of this, but what I've gathered is that mobiles can now use an XML format file (or two, not sure) to specify more details about favicons and behavior.

Is this something that should be added to this app or is it completely out of scope? Seen some activity in the forums about struggles here. See here for more details:
https://discuss.enonic.com/t/how-to-set-up-favicons/361

Is it possible to upgrade the application to support enonic XP 7?

Ref this article, transparent sections of favicons turns black on iOS when you save a website to the home screen.

Perhaps we could create the apple touch icons as JPGs instead, so that the background would default to the more sensible white.

It would be nice to have the option of getting absolute rather than relative paths when using the favicon app. For instance when a site is providing a decorator with menus, footers etc to be used on another domain...

I've actually had this on my never ending todo-list for a while. So very pleased to see you did such an excellent job with this.

A few suggestions I had for the app I would make might benefit your app. Do as you please with my ideas, they're mostly just me trying to discuss and weigh pros and cons about them. What do you think?

favicon.ico is a special format, it's perhaps not an image that should be scaled even as that often screws it up. You can ofc use .png and most modern browsers will use that. But I've found loads and loads programs with legacy code still use the .ico file, and only that. Even loads of crawlers out there only assumes people have a favicon.ico file on root. What this does is it adds loads of 404 on my server for that .ico file on root. So my point here is that it might be valuable to still serve favicon.ico (from root with a url filter) and because of it's tiny scale - let user control it separately (if they want, ofc).

What do you think?