Problem when using uss variables in runtime

UI UI Toolkit
,
1

I used to change the theme rewrite the classes. For example:
original theme uss file

.something-class {
    background-color: var(--something-color-1);
}

new theme uss file

.something-class {
    background-color: var(--something-color-2);
}

Next, to change the theme, I added a new uss file to uxml

somethingUXML.root.styleSheets.Add(newThemeUSS)

It is clear that there can be many things in a class. So I thought I’d update my way of changing the theme. I thought that I could move the color variables to the usual place and override them, rather than entire classes. For example:
original theme file

:root {
    --background-color__something-class: var(--something-color-1);
}

.something-class {
    background-color: var(--background-color__something-class);
}

new theme uss file

:root {
    --background-color__something-class: var(--something-color-2);
}

For some reason it doesn’t work for all files when I add files from code like this
original theme file

:root {
    --background-color__background: var(--background-color-white);
}

#Background {
    background-color: var(--background-color__background);
    width: 100%;
    height: 100%;
    position: absolute;
}

new theme uss file

:root {
    --background-color__background: var(--background-color-black);
}

But when I add in the editor manually everything works fine. Why doesn’t this work when added from code? How to do it right?

2

Maybe there is a way to update all classes after changing variables?

3

Try removing the old stylesheets first, before adding new one. (at least it worked for me)

4

It didn’t work for me.

When I remove the old style sheet, then add the new one and revert the old one, the result looks similar.

But I found an amusing coincidence. If you swap the old and new styles in the editor, the result looks the same as with any of the methods of adding from the code. It’s like the code keeps adding it in the wrong order, no matter what I add first.

5

Corrected the mistake. The top-level uxml file didn’t have my old style definition, so for some reason the uxml kids didn’t have it either, although judging by the editor it exists there. Strange behavior