[Bug 840659] Re: Use symbolic icons in history buttons

[Matthew Paul Thomas]

Ha, I was just thinking about this on Friday. But one thing gives me
pause: If this is an appropriate place to use symbolic Back and Forward
icons, when would ever be an appropriate place to use the non-symbolic
Back and Forward icons? It's reasonable to have an icon for which there
would never be occasion to use a symbolic variant. But to have a
symbolic icon for which you'd never use the non-symbolic original seems
like the icon equivalent of a code smell.

I suppose you could say that the Back and Forward icons should be
monochrome in USC in particular, because the other icons in the
navigation bar are. That would be a valid reason, though not a strong
one. They're different kinds of buttons, so it's visually understandable
that they'd use different styles of icon.

An alternative solution might be for even the non-symbolic Back and
Forward icons to be monochrome (with mono-dark providing a ~white one,
mono-light providing a ~black one). Those particular icons are highly
obvious from their shape, and their current color doesn't imbue any more
meaning to them. (If they were being meaningfully colored, they would be
green, not orange.) In other words, not only should Back and Forward
icons be ~white in USC in Ambiance, they should automatically be ~white
in Firefox in Ambiance too. What do you think, Daniel?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to software-center in Ubuntu.
https://bugs.launchpad.net/bugs/840659

Title:
  Use symbolic icons in history buttons

Status in “software-center” package in Ubuntu:
  New

Bug description:
  The latest USC now uses back and forward arrows from the theme (which
  is great!), but it would be even better if it would use symbolic
  icons. The latest version of Humanity should include both arrow icons
  in -symbolic variants.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/840659/+subscriptions