@adrinux: do you want to update your bulvar branch to try this pull request: https://github.com/daniil4udo/bulvar/pull/42
I've no idea how to properly test a pull request on a released npm…
@adrinux Maybe you can try to fix it by increasing the specifiy of the custom properties so they always overwrite the ones defined by bulma-css-variables:
@dpschen This makes no sense to me. The…
I have an idea what this issue is about.
If I've understood it correctly it's to do with avoiding duplicating the css for every vue component?
It seems that the sass variables are correctly…
There are quite a lot of undefined custom properties. Not just those two.
Both --text and --link are set in bulma-css-variables/sass/utilities/derived-variables.sass
and those derived…
This seems to be related to
--text
not being defined. I think this is a variable that should be defined frombulma-css-vars
?
So that's --text and --link that were missing...I can't help but…
CSS ONLY IMPORTANT: This packages is CSS ONLY!
From digging about in the repo it looks like @bulvar/buefy is very much CSS only. All of Bulma's Sass files still seem to be present in…
Looks like it. Maybe a case for #1064?
Maybe. I'll take a stab at #1064.
We probably want to change it to primary anyway, instead of bulma default blue, so that's all good. But that fact it's not picking it up from bulma is wrong.
Yes, noticed that too. It should be. It's in the Bulma CSS, but I'm not clear how it's set in Bulma Sass - maybe a bug in Bulma-css-variables sass?
See my comment vikunja/frontend#1063 (comment)
I think something basic isn't right - though not sure if that's causing these issues or these are edge cases.…
Looking into 2. And finding that Firefox says var(--link) is not defined. Since link is a bulma variable that makes no sense, something wrong somewhere...and possibly related to @dpschen seeing that…