We have improved color module a lot and taken a big step towards core and contrib themes to leverage it in a way that it is a real asset. #693504: Color.module does not support more than 5 colors and has hard-coded labels

We could do something that might be quite easy and kick a lot of ass:
Say you wanna place an element like a logo in front of a gradient, or any background.

Currently color module supports this only by also calculating the background, cause to my knowledge it only creates PNG 8 images. With support for Internet Explorer slowly fading out, and sure to do much more so during the life cycle of D7.

If we can enable color module to (also?) create PNG 24 that can fade into any background with gradiends and edges, it would make it a lightyear more flexible, especially thinking of trying to make it valuable for contrib theme creators.

While I have been moving back and forth in color.module and don't find it a particularly complicated, am abosutely no coder and cannot say what effort would be needed.

But as color module hardly touches anything but core themes now, it should be non-intrusive and not be called an API change.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

eigentor’s picture

Title: Enable Color module to create png24 - Images without background » Enable Color module to create recolorable png24 Images with transparent background

Of course one can always just use png24 images. The point is - I forgot to mention :P - being able to produce recolorable png 24's.

tim.plunkett’s picture

Version: 7.x-dev » 8.x-dev

Moving.

markhalliwell’s picture

Category: feature » bug
Priority: Normal » Major
Issue tags: +Novice, +Needs backport to D7

I actually consider this to be a major bug given the day and age we're in.

markhalliwell’s picture

xjm’s picture

Category: bug » feature

Hmm, I'm not sure this is a major bug. It's definitely more of a feature request, as this is something we've never supported before, and there's nothing specifically broken without it other than not having this valuable functionality.

So, I'm moving it to major feature request. We might also be able to make the case for it being a normal task, based on the idea that users would expect this functionality, but it's not a major bug nor a major task in my assessment.

manu4543’s picture

Assigned: Unassigned » manu4543
Category: feature » bug
xjm’s picture

Category: bug » feature

Looks like a crosspost; fixing.

xjm’s picture

Category: feature » bug
Priority: Major » Normal

@Mark Carver and I discussed this more in IRC, and he explained that this is more of a bug because Drupal is not respecting the transparency of the image the user provides. So we agreed on normal bug. Sorry for the noise. :)

jair’s picture

I am unable to reproduce this bug.
I uploaded a png24 file (logo_png_24.png) as a custom logo in Bartik and saved
The site logo changed (see screen shot) as expected.

markhalliwell’s picture

This has to do with color support with a theme's default logo the color.module (edit: not uploading a new logo via the UI). I'll need to right up some steps to reproduce.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

pameeela’s picture

Issue summary: View changes
Status: Active » Postponed (maintainer needs more info)
Issue tags: +Needs issue summary update, +Bug Smash Initiative

I can't work out whether this is still valid because I'm not so sure of the use case. Can anyone who knows about these things update the issue summary, or close if this is no longer relevant?

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Assigned: manu4543 » Unassigned
Status: Postponed (maintainer needs more info) » Closed (outdated)

There has been no activity here, expect to ask for more information, for 9 years.

More information about this issue was asked for in #19, 1 year ago. No additional information has been supplied, therefor closing as outdated.

If you are experiencing this problem on a supported version of Drupal reopen the issue, by setting the status to 'Active', and provide complete steps to reproduce the issue (starting from "Install Drupal core").

Thanks!