About color : there are big issue with usage of text-success and text-info with a lot of admin or Fruity template …

Yes, you're right. If I recall right, for example some warnings are in red, some in green. Do you already have a list of points that could be changed?

No sorry :)

I must check , come back here when it‘s done

Same issue in 3.X :

1. text-primary and text-info and text-success are near same
2. difficult to tell if bg-primary is success or not
3. btn-primary and btn-info and btn-success are near same
4. Success row show bigger (issue in statitictics.css)

Some other issue

See https://gitlab.com/Sondages.Pro/checkAdminBootstrapColor for view sample

Capture d’écran du 2019-06-17 09-44-40.png (27,423 bytes)   

Capture d’écran du 2019-06-17 09-44-40.png (27,423 bytes)   

Capture d’écran du 2019-06-17 09-44-51.png (23,946 bytes)   

Capture d’écran du 2019-06-17 09-44-51.png (23,946 bytes)   

Capture d’écran du 2019-06-17 09-48-37.png (7,846 bytes)   

Capture d’écran du 2019-06-17 09-48-37.png (7,846 bytes)   

Why success of Bay of many is blue ?

In home page settings, those are switches. In the global settings those are buttongroups.
I would back your proposal to use a dark shade of the main color as a background for the selected option.
This has to be talked about in the team, though.

The LimeSurvey color scheme is based on a monocolored scheme, meaning success and primary are the same colours, and Info being a gradient of that color.
This was so since LS2.5. It is also repeated in the fruity themes based on the backend colors.
We won't change this in LS4.

meaning success and primary are the same colours

But why remove a colour of Bootsrap ? Succes and primary didn't have same meaning …

Ok, but still : no difference between success/primary or danger/primary make it very complex to use …

See for sample
bootswatch Journal : primary red, danger orange
bootswatch Cosmo : primary blue, info purple
bootswatch United : primary orange, danger darker red

And still :

1. table Success row show bigger (issue in statitictics.css)
2. Why success of Bay of many is blue ?

Because :
The LimeSurvey color scheme is based on a monocolored scheme, meaning success and primary are the same colours, and Info being a gradient of that color.
Also this is the scope of a new ticket.

So there won't be no selected options in green due to an unchangable color scheme?

No, but I recommend we talk about this in a meeting.
I have no strong feelings or arguments about this, so i'd put it up for the developer/contributer vote.

To be honest, I would even call this a regression. At LS 3 we have green/red colors for on/off which is pretty intuitive. At LS 4 this is now missing which will confuse users.
Please make sure LS 3 and LS 4 interface colors do not differ.

+1
I was just testing question types in RC6 and found green for "no" and red for "yes" quite confusing. Furthermore, it is sometimes stil unclear when an option is selected and when not. See screenshot below.

grafik.png (13,528 bytes)   

grafik.png (13,528 bytes)   

Anout slider , think best is to allow color by option.

Sometimes : Yes is OK, but another time Yes is danger :)

I have set this ticket to "block" because I really think we should not release a first alpha version before such things are fixed.

@DenisChenu: You're perfectly right. One solution to this could be to change the wording of certain options so that yes/no or red/green is more consistent. Negative formulations should be avoided as cognitive processing is much harder. This should be considered when designing UI elements.

For example, I still find the option "hide tip" quite confusing and I am sure that "show tip" is much easier to understand. I guess that the button label reflects the way this option is programmed (with a hide == true and not with show == false).

@f_funke: I second those thoughts. The new release is nearly ready but that would be the perfect option to adjust things like this. So please bribe the development team with some beers to put some more effort into adjusting this.

@cdorin, I just created this ticket (https://bugs.limesurvey.org/view.php?id=15913) which is a child of the given ticket here.
Since this is considered a regression and the colors are really misleading, please add this ticket to the next sprint.

The color (font and background) of the enabled state button should be the one from the normal ok button . (for the button groups)
In another task later we will unify the switches (which use green and red) to use the same button groups.

The color (font and background) of the enabled state button should be the one from the normal ok button . (for the button groups)

Info color ? Or primary color ?

The color (font and background) of the enabled state button should be the one from the normal ok button . (for the button groups)

If user have color issue : maybe we need to add a font awesome element ?

Info color ? Or primary color ?
Success Color.

Why ? I think info is better : why it's better to show slider in reverse position ? Why it's a success ?

And if it's better : why it's dangerous to say at default (No) ?

Carsten decided first to use the normal ok button color. And that's success.

OK :)

Yeah, question would be rather why the OK buttons have success color.

If I Look at Boostrap color theme explanations at https://getbootstrap.com/docs/3.3/css/#buttons
they should have 'Primary' color.

But that is another problem :-)

Branch: bug/14984-admin-backend-color-of-selected-options-is-confusing

Changed the background color to the color of the selected theme. Green would be too 'hard' for the eyes. Consider, you would select an blue colored theme - then it would break the UI, if I only changed the color to green (primary). So its now 'smoother' for your eyes.

Please check out my branch, if you want to test it.

Green would be too 'hard' for the eyes.

It's not a question of smoother ;: it's a question of meaning …
text-success : green
text-danger : red

https://bootswatch.com/united/

So its a question of usability - red and green would be confusing in a blue theme. Check out the branch and you will see. Its better than only red or green. Now you really see that active button is really activated. Its not like before ;)

:+1: for default color

Then in question advanced settings : replaced by default button ?

Capture d’écran_2021-03-23_16-25-30.png (3,767 bytes)   

Capture d’écran_2021-03-23_16-25-30.png (3,767 bytes)   

PS : sometimes rev VS green can be great : Filter HTML for XSS or Force HTTPS etc …

Then we would need alternatives for every theme - which should look also good - and which dont break the UI/UX. But this is something for later - I will add this to my task list. Thanks :)

Then we would need alternatives for every theme

No just use boostratp default success / danger / warning / info / primary

about chjecked VS not checked : seems more a global boostrap issue (see https://bugs.limesurvey.org/view.php?id=14984#c54287 comemnt)

Maybe we can update btn color at same time we add/remove the active button ?

Capture d’écran_2021-03-23_16-45-13.png (57,068 bytes)   

Capture d’écran_2021-03-23_16-45-13.png (57,068 bytes)   

btn-info clearer sample (with Green/default at install)

Capture d’écran_2021-03-23_16-47-11.png (46,218 bytes)   

Capture d’écran_2021-03-23_16-47-11.png (46,218 bytes)   

BS5 : https://getbootstrap.com/docs/5.0/components/button-group/#checkbox-and-radio-button-groups
BS3 : https://getbootstrap.com/docs/3.3/components/#btn-groups

button clean difference is more a BS issue