One technical constraint that we have is that icons are (currently) monochrome, and their color changes depending on the context (to color-base in most cases, but icons in buttons can also be white, or various shades of blue or red). Right now the icon versions of the logos are monochrome for this reason. We could, in theory, have a few icons that are not monochrome and whose color doesn't adapt to the context, but that would be confusing because those icons could not be used with buttons (especially primary and disabled buttons where the icon needs to be white).

In T338300#8915451, @Catrope wrote:

One technical constraint that we have is that icons are (currently) monochrome, and their color changes depending on the context (to color-base in most cases, but icons in buttons can also be white, or various shades of blue or red). Right now the icon versions of the logos are monochrome for this reason. We could, in theory, have a few icons that are not monochrome and whose color doesn't adapt to the context, but that would be confusing because those icons could not be used with buttons (especially primary and disabled buttons where the icon needs to be white).

Adding this info as "Consideration" in the task description.

For this reason, I think we should not add the logos as icons and we should use instead the icon version in any component or in any place where we are using icons. E.g. lists, menus, buttons, selects, etc. On the other hand, we could use the logos when we place them in a standalone way (e.g. header).

In T338300#8917952, @bmartinezcalvo wrote:

In T338300#8915451, @Catrope wrote:

One technical constraint that we have is that icons are (currently) monochrome, and their color changes depending on the context (to color-base in most cases, but icons in buttons can also be white, or various shades of blue or red). Right now the icon versions of the logos are monochrome for this reason. We could, in theory, have a few icons that are not monochrome and whose color doesn't adapt to the context, but that would be confusing because those icons could not be used with buttons (especially primary and disabled buttons where the icon needs to be white).

Adding this info as "Consideration" in the task description.

For this reason, I think we should not add the logos as icons and we should use instead the icon version in any component or in any place where we are using icons. E.g. lists, menus, buttons, selects, etc. On the other hand, we could use the logos when we place them in a standalone way (e.g. header).

I generally agree, but would suggest specifying whether or not using logos (not icons) includes the two use cases mentioned in the task, favicons and image links at the bottom of the search results page. This can be not so ideal in certain cases where logos lose legibility at small sizes, but in such cases projects can and have gone with a simplified logo option. See example below where there is a mix of simplified vs regular logo used in favicon.