Closed bryanjonker-illinois closed 4 weeks ago
The page CSS in the demo is more specific than the CSS in the component, so in some ways it's working as intended.
The rule overriding the color is ilw-page[illinois] main h2
, which has a high specificity. I think we're better off coming up with rules on how these are handled than just increasing the specificity.
For example, the ilw-page
rule could override the --ilw-heading--color
variable rather than the color
CSS. That way the component, which sets a different variable as the color, would retain its customization without a CSS specificity race.
Note -- was happening because there was an extra <div>
in the markup. Going to make the rules more generic.
https://builder3.toolkit.illinois.edu/sample_page/index.html and https://builder3.toolkit.illinois.edu/sample_page_alternate/index.html
Can you ensure that the font stays the same in the call to action component? It looks like the page is overriding something. Thanks!