Refactor references to images in Claro's images/core directory

Created on 5 May 2020, over 4 years ago
Updated 13 May 2024, 7 months ago

Sorry it took me a while to review this. The patch applies, but it's actually changing the color for several icons with different level of visual implication.

Problem/Motivation

In #3045216: Asset paths pointing to core/misc folder assume Claro is installed in core/themes the images/core directory was created for containing copies of core icons used by Claro. These copies existed because Claro was a contrib module and it's location relative to /core was not consistent.
images/core has a readme that states

Icons in this folder are copied from Drupal core. This folder with its content
should be removed before moving Claro to Drupal core

Claro is now in Drupal core, so this change can happen.

Proposed resolution

  1. In Claro's CSS Change all references to icons images/core to use the ones in core/misc/icons
  2. Remove Claro's images/core directory

Remaining tasks

📌 Task
Status

Closed: outdated

Version

11.0 🔥

Component
Claro 

Last updated 2 days ago

Created by

🇺🇸United States bnjmnm Ann Arbor, MI

Live updates comments and jobs are added and updated live.
  • Needs frontend framework manager review

    Used to alert the fron-tend framework manager core committer(s) that a front-end focused issue significantly impacts (or has the potential to impact) multiple subsystems or represents a significant change or addition in architecture or public APIs, and their signoff is needed (see the governance policy for more information). If an issue significantly impacts only one subsystem, use Needs subsystem maintainer review instead, and make sure the issue component is set to the correct subsystem.

Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • The Needs Review Queue Bot tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

    Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

    Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.

  • 🇮🇳India gauravvvv Delhi, India

    Patch #31, no more applies to 10.1.x. because some files doesn't exist in 10.1.x. Adding patch for 10.1.x. Please review

    git apply -v 3133823-31.patch
    Checking patch core/themes/claro/css/components/details.css...
    Hunk #1 succeeded at 477 (offset -102 lines).
    Checking patch core/themes/claro/css/components/details.pcss.css...
    Hunk #1 succeeded at 449 (offset -106 lines).
    Checking patch core/themes/claro/css/components/system-admin--status-report.css...
    Checking patch core/themes/claro/css/components/system-admin--status-report.pcss.css...
    Hunk #1 succeeded at 48 (offset -2 lines).
    Checking patch core/themes/claro/css/components/system-status-counter.css...
    error: while searching for:
    }
    
    .system-status-counter__status-icon--error:before {
  • Status changed to Needs review almost 2 years ago
  • Status changed to Needs work over 1 year ago
  • 🇺🇸United States smustgrave

    Think patch #34 is missing some changes. The patch is much smaller then #23.

    Think somethings were removed in #31

    From what I can tell the new images aren't there.

  • Status changed to Needs review over 1 year ago
  • 🇮🇳India gauravvvv Delhi, India

    I have added the missing SVG image. please review

  • 🇮🇳India Santosh_Verma

    Tested the Patch #37 and getting error while patch applying

  • 🇮🇳India gauravvvv Delhi, India

    fixed build error. attached interdiff for same.

  • Status changed to RTBC over 1 year ago
  • 🇺🇸United States smustgrave

    Missing changes have been added back.

  • Status changed to Needs work over 1 year ago
  • 🇪🇸Spain ckrina Barcelona

    Sorry it took me a while to review this. The patch applies, but it's actually changing the color for several icons with different level of visual implication.

    1. +++ b/core/themes/claro/css/components/system-status-report-general-info.pcss.css 
      @@ -41,17 +41,17 @@
      +  background-image: url(../../images/icons/cccccc/clock.svg);
      

      This shouldn't be changing the icon color from white(#fff) to #CCC. So it should land on the existing folder /ffffff.

    2. +++ b/core/themes/claro/css/components/system-status-report-general-info.pcss.css
      @@ -41,17 +41,17 @@
      +  background-image: url(../../images/icons/cccccc/server.svg);
      

      Same, this shouldn't be changing the icon color from white to #CCC. So it should land on the existing folder /ffffff.

    3. +++ b/core/themes/claro/css/components/system-status-report-general-info.pcss.css
      @@ -41,17 +41,17 @@
      +  background-image: url(../../images/icons/cccccc/php-logo.svg);
      

      Same, this shouldn't be changing the icon color from white to #CCC. So it should land on the existing folder /ffffff.

    4. +++ b/core/themes/claro/css/components/system-status-report-general-info.pcss.css
      @@ -41,17 +41,17 @@
      +  background-image: url(../../images/icons/cccccc/database.svg);
      

      Same, this shouldn't be changing the icon color from white to #CCC. So it should land on the existing folder /ffffff.

    5. +++ b/core/themes/claro/css/components/system-status-report.pcss.css
      @@ -60,10 +60,10 @@
      +  background-image: url(../../../../misc/icons/e32700/error.svg);
      

      Why is this changing the color from #dc2323 to #e32700? I understand this is to reuse the default core icon, but it's actually changing the red used in Claro. Meaning it's changing the designs. Both icons still exist in core, so please keep the same color. Another question is way we keep the same icon in core with similar reds, but that should be solved in another issue :)

  • 🇪🇸Spain ckrina Barcelona

    I forgot to reference a related issue for Claro related to icons: #3269881: Update icon colors with the new color scale

  • 🇮🇳India Akram Khan Cuttack, Odisha

    added patch and address #41

  • 🇮🇳India Akram Khan Cuttack, Odisha

    try to fix CCF #41

  • 🇬🇧United Kingdom robcarr Perthshire, Scotland

    Thank you for all the work on this issue. I've tried most of the recent patches against D10.1-beta1, and cannot get them to apply.

  • Open in Jenkins → Open on Drupal.org →
    Environment: PHP 8.1 & MySQL 5.7
    last update over 1 year ago
    Patch Failed to Apply
  • Status changed to Needs review over 1 year ago
  • last update over 1 year ago
    29,417 pass
  • 🇮🇳India gauravvvv Delhi, India

    I have provided patch for 11.x, addressed #41. please review

  • Status changed to Needs work over 1 year ago
  • 🇺🇸United States smustgrave

    From what I can tell the images are still landing in cccccc

  • Status changed to Needs review 8 months ago
  • 🇮🇳India gauravvvv Delhi, India

    Addressed #48, please review

  • Pipeline finished with Success
    8 months ago
    Total: 728s
    #161249
  • Status changed to Closed: outdated 7 months ago
  • 🇺🇸United States bnjmnm Ann Arbor, MI

    When I filed this issue in 2020...

    • Claro was an experimental theme. It has since become Drupal's admin theme
    • I was not a frontend framework manager. I have since become a frontend framework manager

    Given that it is 2+ years since Claro graduated from experimental status, I'm not sure the benefits of of moving the assets + references outweigh the potential disruption. Testing this manually requires time and it is a lengthy process without tests to confirm things are OK. Something unwanted could slip through, and custom modules/themes may be referencing some of these assets. Had this happened while Claro was still experimental I'd be all for the change. While it should have occurred when Claro was added to core on October 4, 2019, that doesn't necessarily mean it should happen now. I'm setting this to Closed (outdated), but I don't intend this to be a stern "final word". If anyone here believes the benefits of doing this outweigh the risks then document that and re-open.

    Alternatively, get some quick issue credit and open an issue that simply removes this from the readme:

    Icons in this folder are copied from Drupal core. This folder with its content
    should be removed before moving Claro to Drupal core
Production build 0.71.5 2024