Problem/Motivation

If a user selects a Bootswatch theme, the overrides.css file that is supplemented afterwards causes the Bootswatch theme to look "broken". This is because the overrides.css file is compiled with the default Bootstrap variables and not any of the Bootswatch theme variables.

Proposed resolution

Provide a unique CSS override file for each Bootswatch theme/version.

Remaining tasks

TBD (Postponed on #2348843: Add Grunt for project maintainer workflow)

User interface changes

TBD

API changes

TBD

Comments

markhalliwell’s picture

markhalliwell
Primary language English
commented
Priority: Major » Normal

While this is a nice to have, it really shouldn't be blocking releases.

  • markcarver committed 2276b0d on 7.x-3.x 
    Issue #2462635: CSS overrides isn't compatible with Bootswatch themes...

  • markcarver committed e0639dd on 8.x-3.x 
    Issue #2462635: CSS overrides isn't compatible with Bootswatch themes...
markhalliwell’s picture

markhalliwell
Primary language English
commented
Status: Postponed » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

Anticosti’s picture

Anticosti commented

Greetings,
Live CSS Version: 7.x-2.12, could be an interesting alternative for you.
It works for me with Firefox.
Does not work with Google Chrome.

May this help...

markhalliwell’s picture

markhalliwell
Primary language English
commented

Thanks. We are aware of this module, however themes cannot officially depend on modules, nor do we wish to make this base theme dependent on such modules. This issue is also just about supporting out-of-the-box sub-themes that use the CDN by default (which means no extra installs).