#5928 - Monochrome icons setting should not apply to Social sharing icons

This is a spacer post for a website comment topic. The content this topic relates to: #5928 - Monochrome icons setting should not apply to Social sharing icons
I'm confused.

You mentioned making these not monochrome (e.g. orange and blue), but then mention the orange and blue icons are too busy. And the social share icons are already monochrome (one color).
The social share icons (other than the internal composr ones) are close to their brand colours and it makes sense for these icons to stand out (imo). I am personally not keen on the forced blue/orange icons (which may conflict with people's choice of theme colour) when applied to the whole site. Would be nice to have a config option for the main_screen_actions block social icons and the rest of the icons can stay monochrome (the default) if they aren't going to respect the seed colour as per v10. It seems to be a choice between every icon being in blue/orange, or not.

I plan to change the icons to https://simpleicons.org/ as they have correct branding colours and up-to-date logos (ie, X), but as a general point I think the config option might be useful given the importance of sharing on 3rd party platforms (for those who aren't going to change the icons).

Image

(Click to enlarge)

So if I'm understanding correctly, you'd like an option that allows you to make the social share icons *not* monochrome if the icons around the rest of the site *are*?
Yes, that's what I mean. As these are recognised icons it makes sense for them to carry the brand colours and stand out if the rest of the site is using monochrome icons.

I can see that being useful. Not likely something I'll implement in 11.0 considering how far along I am (unless I get sponsored to do so), but it may be a v11.1 feature or a rolling (submarine) one I slip into a v11.0 patch release.
Also of note, after unselecting monochrome icons to see the coloured versions I have tried to once again enable monochrome icons. The setting is not being applied. Emptied all the caches.
That sounds like a bug. Can you add that as a separate tracker issue so it doesn't get buried in the comments of this one?
0 guests and 0 members have recently viewed this.