Yes, I think providing a static image once is sufficient. Like a MirGraphicsRegion.
However there is no good reason to limit the number of times an app can upload a new icon. Certainly you would create bugs by limiting when and where the icon gets set. An app is allowed to set its icon at any time, and failure to honour that is a shell bug - not something we could or should ask app developers to fix if their app has worked perfectly elsewhere for years. So I understand your concern, but solving the impersonation problem is worse than not solving it :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1607199 Title: Add support for apps supplying their icons at run-time Status in Canonical System Image: New Status in Mir: Triaged Status in Ubuntu UX: New Status in mir package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Triaged Bug description: Add support for apps supplying their icons at run-time. X apps (and thus GTK apps) like to provide their app icons at run- time. We don't yet have the infrastructure to support this. But you can see the bitmaps by just running 'xprop' and clicking on a window. https://specifications.freedesktop.org/wm-spec/wm-spec- latest.html#idm140200472568384 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607199/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
