Comment 3 for bug 1284233

The use case is to use Icon directly (without any wrapper around it to check for image://theme/ in the uri) and its colourization feature, when the actual path for the icon comes from a remote service (e.g. indicator services).

And especially *because* other components support both iconName and iconSource, it would make sense here as well.