Problem/Motivation

In the issue Darker blue color for :hover & :active, we discovered that the value of --color-absolutezero-active was not the same as it is set in the design specs.
This has been fixed, but it is possible that other color values are still incorrect.

Proposed resolution

  • Update colors if they do not correspond with the values set in the design system.
  • Update the comments next to these colors if incorrect.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Issue fork drupal-3085109

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

AntoineH created an issue. See original summary.

ant1’s picture

Status: Active » Needs review
StatusFileSize
new1.44 KB

I updated some of the comments, according to what I've found in the design specs.

saschaeggi’s picture

I just had a look at the patch and can verify that the variables for absolute-zero are now congruent to the Design System, thanks!

saschaeggi’s picture

Status: Needs review » Reviewed & tested by the community
saschaeggi’s picture

Assigned: Unassigned » lauriii
Status: Reviewed & tested by the community » Needs review
lauriii’s picture

Assigned: lauriii » Unassigned
Status: Needs review » Needs work

@saschaeggi pointed out on PM that we don't use the mathematically correct values for the absolute-zero-hover and absolute-zero-active because they would tend to a violet tone. We should document that here as well.

ant1’s picture

Status: Needs work » Needs review
StatusFileSize
new1.75 KB

Updated the comments for --color-absolutezero-hover & --color-absolutezero-active.

ant1’s picture

Version: 8.x-1.x-dev » 8.x-2.x-dev
huzooka’s picture

Project: Claro » Drupal core
Version: 8.x-2.x-dev » 8.9.x-dev
Component: Code » Claro theme
ant1’s picture

StatusFileSize
new56.04 KB

Rerolled.

lokarkristina’s picture

Issue tags: +ContributionWeekend2020
StatusFileSize
new64.7 KB

I updated the color-absolutezero and color-absolutezero-hover to match the designs. I've also updated the color-absolutezero-hover and color-absolutezero-active comments to correct values.

tjasajereb’s picture

Reviewed the latest patch and confirming color--absolutezero, color--absolutezero-hover and color--absolutezero-active are now corrected to match the design files.

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

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now 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.

asmita26’s picture

Assigned: Unassigned » asmita26
asmita26’s picture

Status: Needs review » Reviewed & tested by the community

Verified and tested by applying patch #11. It was applied successfully. color--absolutezero, color--absolutezero-hover and color--absolutezero-active looks good to me and match with design as well.

lauriii’s picture

Status: Reviewed & tested by the community » Needs work
Issue tags: +Needs reroll

I think we need a reroll for 9.1.x 🧑‍🍳

narendra.rajwar27’s picture

Status: Needs work » Needs review
Issue tags: -Needs reroll

Patch at #10 is getting applied for 9.1.x as well.

(EDIT): Ah i see , i checked for patch #10. :( :(

himanshu_sindhwani’s picture

StatusFileSize
new64.5 KB

Reroll for patch at 11 for 9.1.x.

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

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

tanubansal’s picture

Patch #18 is successfully applied for 9.1x
. color--absolutezero, color--absolutezero-hover and color--absolutezero-active looks good and as per design.

bnjmnm’s picture

StatusFileSize
new6.26 KB
bnjmnm’s picture

Assigned: asmita26 » Unassigned

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

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

sakthivel m’s picture

StatusFileSize
new6.26 KB

#24 Just Re-roll the patch 9.3.x

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

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

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

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now 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.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

Status: Needs review » Needs work

Needs reroll for D10.1

akram khan’s picture

StatusFileSize
new2.3 KB
new8.39 KB

Adding updated patch and reroll against 10.1.x

smustgrave’s picture

@Akram Khan seems you removed a number of changes

akram khan’s picture

@smustgrave No i didn't. Changed only that much required in CSS file.
In 10.1.x CSS file has been changed before in 9.x its hardcoded or directly used the css properties and in 10.1.x properties are used using variables so we need to change only in one variable and properties apply every where it's used. please suggest if i'm wrong.

smustgrave’s picture

Status: Needs work » Needs review
StatusFileSize
new2.03 KB
new3.66 KB

Disregard previous comment I see what was done.

But appears the css wasn't compiled. You can check for CI issues using the script in core/scripts/dev/commit-code-check.sh

nod_’s picture

Status: Needs review » Needs work
Issue tags: +Needs issue summary update

Last patch is only changing comments, not the actual color value, is that on purpose?

Kinda lost at what supposed to happen here. Can someone update the IS with a link to claro color palette?

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

rinku jacob 13 made their first commit to this issue’s fork.

rinku jacob 13’s picture

Hi nod_, From understanding the issue from the beginning, we need to change the value of --color-absolutezero-active because in the issue(Darker Blue color for hover & active) , @saschaeggi mentions that the hover color should be #0036B1 and the active color should be #00339A. However, based on comment #11, she updated the color codes for both hover and active states according to the Figma design: Despite this, the recent patches haven't updated the active color value. Therefore, I didn't change the active color code. Should we proceed with updating the active color value as well? "I have created a merge request based on the recent patches, which means I only made changes to the hover color. The latest version of Drupal uses #002e9a as the active color value.

rinku jacob 13’s picture

Status: Needs work » Needs review
smustgrave’s picture

Status: Needs review » Needs work
Issue tags: +Needs subsystem maintainer review

We should have a summary update for this one.

Probably good to get a sub-maintainer to sign off on changes after a few years.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.

quietone’s picture

Status: Needs work » Postponed

The Claro theme was approved for removal in #3576460: [policy, no patch] Deprecate and remove Claro.

This is Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.

The deprecation work is in #3576668: [meta] Tasks to deprecate Claro and the removal work in #3584638: [meta] Tasks to remove the Claro theme.

smustgrave’s picture

Project: Drupal core » Claro
Version: main » 3.0.x-dev
Component: Claro theme » Code
Status: Postponed » Needs work

Claro has moved to contrib