text on some buttons has primary color

[szaimen]

Not sure if it is meant to be this way

See

Or

[szaimen]

This is especially a problem when a light color was chosen:

[juliusknorr]

In case of the light value it is probably using --color-primary-* instead of --color-primary-element-* as the css variables

Depending on their use we may want to switch to tertiary styles:
https://nextcloud-vue-components.netlify.app/#/Components/NcButton

[szaimen]

This seems to be a problem with all secondary buttons which is the default button if not specified. cc @nextcloud/server-frontend do you have a workaround or idea how to solve that? cc @jancborchardt as well...

[jancborchardt]

In general, what needs to be fixed is as Julius said above, so move from --color-primary-* to --color-primary-element-*

For the Dashboard buttons, we need to make the weather and edit settings buttons look like the "Set status" button

• switch to color-main-text
• make the text not bold
• adjust the background to translucent

[szaimen]

Do I need to adjust this in the vue component or somewhere in server?

[jancborchardt]

@szaimen the feedback part on the dashboard buttons is specific to Dashboard, so server.
The part Julius mentioned I assume goes into nextcloud-vue. cc button expert @marcoambrosini

[szaimen]

I had a look and the weather button is an unmodified secondary button. The set status button on the left is not.

So this likely needs fixing in the vue components.

cc @marcoambrosini

[jancborchardt]

@szaimen as said, this means that it needs customization in the Dashboard app. :) The button for weather and customize on the bottom should be like "Set status", not the other way around.

What it needs is something like this, and then additionally an adjustment of the background on the customize button on the bottom:

#app-dashboard #status-weather .button-vue__text,
#app-dashboard .footer .button-vue__text {
  font-weight: normal;
  color: var(--color-main-text);
}

[marcoambrosini]

This is similar to the settings button in the navigation. Here's how we did it. Probably we should introduce this as a use-case in the library

Why not bold @jancborchardt ?