style-sheet | ️ Fast styles in JavaScript with support for static CSS | Frontend Framework library

The issue is that you are calling useStyles from both Cell and Value. This causes two different classes to be generated for the value rule and two different classes to be generated for the static rule. The value class generated for Cell is being referenced by "& $value" in the static class applied to Cell, but it is the value class generated for Value that is applied to the Value element, so it isn't matched by the descendant selector in the static class.

You can fix this by only calling useStyles in one place and passing the value class name down to the Value element as in the example below:

What you want to do is merge your interfaces.

In your declarations.d.ts file, include the following

To better understand refer to the specification where you can read:

1. If the cascade results in a value, use it. Except that, if the value is 'inherit', the specified value is defined in “The 'inherit' value” below.

The cascade is more explicit than the document's style sheet.

If you continue in the specification you will find:

Author. The author specifies style sheets for a source document according to the conventions of the document language. For instance, in HTML, style sheets may be included in the document or linked externally.^ref

So it's clear that all the CSS is considered even the internal styling and the inline one which is logical.

You can see the rules as follow:

1. If a CSS is applied to the element we use it
2. If nothing is applied we see if the property is inherited. If yes we use the value from the parent. If no we use the initial value.

Try it:

It turns out it was an issue with our babel.config.js. We were adding the babel-plugin-css-modules-transform plugin, which apparently superseded the moduleNameMapper entry.

A possible solution is to use a QProxyStyle to modify the painting:

This fix is to provide the header and the footer twice once for TOC and once for the contents themselves

Your suspect is indeed correct: when using stylesheets, many widget properties are ignored, both for their getters and setters.

There is no direct way to know those values, as they all are managed internally by Qt's parser.

Most importantly, the palette() and font() (as fontMetrics(), obviously) are not affected, so you cannot know what are the font properties or the palette colors used for the stylesheet, and if you try to set the font or set a new palette you'll get no result (all this assuming that you're actually setting some color or font in the stylesheet, obviuosly).

This is also valid for other widget specific properties (for example, the QFrame border style), which might even have slightly different results on different styles/systems.

An this is also the reason for which you should either use stylesheets or a QPalette, as mixing them might result in unexpected behavior.

From QWidget.palette() docs:

Warning: Do not use this function in conjunction with Qt Style Sheets.

From QWidget.font() docs:

Note : If Qt Style Sheets are used on the same widget as setFont(), style sheets will take precedence if the settings conflict.

Sorry for the runaround but this is a bit of bad news...

I completely forgot that we don't support shadow color in the resource file. It's a part of the developer API for the round rectangle class but it never propagated into the resource file. So it isn't supported by the designer tool or the CSS code.

You have two workarounds you can take:

1. Edit the component and change the borders RoundRectBorder instance to include the shadow color. This will mean doing it for every component instance of that type...

2. Use standard CSS shadow tags. This would mean the CSS will generate images instead of a border entry. It will enlarge your resource file and slow down CSS compilation. It might look worse for some cases.

You can also try to submit a PR with the changes to the resource file and additional CSS support. Although that would require a bit of effort.