touch-packages team mailing list archive

[Rodney Dawes <1531913@xxxxxxxxxxxxxxxxxx>]

Specifying a blank artwork is still possible, and still not sensible.
One can always specify a 1x1 transparent image as the artwork for
intentionally blank space. :)

We don't detect that we are sending an empty image. We just specify the
fallback and expect it to work as a fallback should. If a fallback is
not shown when no artwork is passed, then it's not a fallback. If it's
the image to be shown when there is an error loading the image, then the
API is wrong, because developers might want to show something else in
case of error, so that it's known there was an error. Changing the scope
to do the work would mean duplicating code and logic. Why should we have
to specify the image that we want to fall back to, in two completely
different ways, in the same code?

** Also affects: canonical-devices-system-image
   Importance: Undecided
       Status: New

-- 
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/1531913

Title:
  Fallback image not shown when no image specified

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  In fixing bug #1520631 in unity-scope-click, as the store server will
  start allowing uploads with no icon specified, it was discovered that
  Unity8 is not showing the fallback when we do not include the artwork.
  Instead, it is only shown if we specify invalid artwork. This seems
  wrong, and instead I would think the fallback would be displayed
  whenever no other artwork is provided.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1531913/+subscriptions