On Saturday, September 21, 2013 at 8:21 AM, Jonas Sicking wrote:
> We do allow updating icons on application update, so I don't actually > see any additional security risks with dynamic updates of icons. > The use case demonstrated in the JS library is one that seems very closely related to notifications (i.e., compositing a number on top of an icon to notify the use of some significant event). This seems better left to the platform, specially as such things can be automatically handled (and localised) by the user agent (and notifications can be stored safely across restarts, thus allowing such decorations to be generated without needing the application to be opened at all). I'm wondering if there are other use cases that are missing? E.g., would we want to have something similar to MacOs's activity monitor, in which an icon is updated dynamically as memory or CPU usage changes? This would require some kind of background worker that is able to update the icon periodically, which doesn't seem to me like a good idea on a constrained device. Also, at least in FxOS, one is not able to view the icon of the application while the application is running. > Instead we keep the application name constant as long as the app is > installed. > Does this apply also to updates? If not - it seems logical that an application should be able to change its name over versions, specially if it assists with usability and findability across versions (i.e., "my crappy named app", after lot's of user complaints, should be able to be renamed to "my awesomely named app" - there may be other reasons why an app might need to be renamed, like an accidental copyright violation in some region the author didn't know about, etc.). Kind regards, Marcos -- Marcos Caceres _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
