Contrib.social

Wrong order of CSS Aggregation?

Open on Drupal.org →
Created on 29 August 2021, over 3 years ago
Updated 15 August 2024, 9 months ago

Problem/Motivation

Selecting the performance option Aggregate CSS files I noticed that the CSS class body gets the wrong attribute for background-color. The theme I use is custom-made based on Bartik.

Steps to reproduce

The behaviour without the aggregation option set is that the background-color-value is first taken from /sites/default/files/color/bartik-a538a93c/color.css?qylesa (line 3), and then overwritten by the value from /sites/themes/theme_name/css/color.css?qylesa which gives the correct resulting background-color-value.

The behaviour with the aggregation option set is that the background-color-value is taken from /sites/default/files/css/css_psOWaDjpfL8HLt18ElJqFpCGsHGxnKq-mZuZqFpsr8.css (line 82) which gives the incorrect background-color-value from the Bartik theme and not from the Custom Theme.

I have no clue to what the root-cause of this behaviour is.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

🐛 Bug report
Status

Closed: cannot reproduce

Version

11.0 🔥

Component
Asset library  →

Last updated 3 days ago

No maintainer
Created by

🇳🇱Netherlands Frank@Drupal

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

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

  • Comment over 1 year ago →
    🇬🇧United Kingdom catch

    The subtheme isn't setting an explicit dependency on bartik's library, so the order isn't guaranteed - just being in a subtheme doesn't guarantee the order. Setting back to needs more info - if the dependency fixes the issue, then I think this is working as designed.

  • Status changed to Closed: cannot reproduce 9 months ago
  • Comment 9 months ago →
    🇦🇺Australia acbramley

    Thanks for reporting this issue. We rely on issue reports like this one to resolve bugs and improve Drupal core.

    As part of the Bug Smash Initiative, we are triaging issues that are marked "Postponed (maintainer needs more info)". This issue was marked "Postponed (maintainer needs more info)" more than 1 year ago.

    Since we need more information to move forward with this issue, I am closing it.

    Please feel free to reopen with more information.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024