View Issue Details

IDProjectCategoryView StatusLast Update
14984Bug reportsOtherpublic2020-02-25 09:05
Reporterf_funke Assigned To 
PrioritynoneSeveritycrash 
Status newResolutionopen 
Product Version4.0.0-beta 
Summary14984: Admin backend: Color of selected options is confusing
Description

The color of switches in the admin backend is really confusing. Grey means active, which might be clear when there are at least three options, but whenever there are only two options (e.g., on/off) it looks as if the other option was activated. It would be good to use lime-green as in the homepage settings.

TagsNo tags attached.
Complete LimeSurvey version number (& build)4.0.0-beta github 190614
I will donate to the project if issue is resolvedNo
Browser
Database & DB-VersionmySQL LimeSurvey DB 416
Server OS (if known)
Webserver software & version (if known)
PHP Version7.2.7

Relationships

related to 15913 new Survey details overview at LS4 shows text with misleading color 

Activities

f_funke

f_funke

2019-06-16 16:34

developer  

Colors_for_switches_190616.png (32,279 bytes)   
Colors_for_switches_190616.png (32,279 bytes)   
DenisChenu

DenisChenu

2019-06-17 08:00

developer   ~52423

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

f_funke

f_funke

2019-06-17 08:34

developer   ~52424

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?

DenisChenu

DenisChenu

2019-06-17 08:48

developer   ~52425

No sorry :)

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

DenisChenu

DenisChenu

2019-06-17 09:49

developer   ~52426

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

DenisChenu

DenisChenu

2019-06-17 09:50

developer   ~52427

Why success of Bay of many is blue ?

markusfluer

markusfluer

2019-07-12 11:08

administrator   ~52860

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.

DenisChenu

DenisChenu

2019-07-12 11:23

developer   ~52861

Last edited: 2019-07-12 11:25

View 3 revisions

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 ?
markusfluer

markusfluer

2019-07-12 11:39

administrator   ~52862

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.

f_funke

f_funke

2019-08-05 11:49

developer   ~53093

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

markusfluer

markusfluer

2019-08-05 16:13

administrator   ~53109

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.

Mazi

Mazi

2019-10-30 19:56

partner   ~54286

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.

f_funke

f_funke

2019-10-30 20:23

developer   ~54287

+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)   
DenisChenu

DenisChenu

2019-10-30 21:53

developer   ~54288

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

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

Mazi

Mazi

2019-10-30 23:17

partner   ~54292

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

f_funke

f_funke

2019-11-01 09:32

developer   ~54305

@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).

Mazi

Mazi

2019-11-01 09:35

partner   ~54306

@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.

Mazi

Mazi

2020-02-25 09:05

partner   ~56195

@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.

Issue History

Date Modified Username Field Change
2019-06-16 16:34 f_funke New Issue
2019-06-16 16:34 f_funke File Added: Colors_for_switches_190616.png
2019-06-17 08:00 DenisChenu Note Added: 52423
2019-06-17 08:34 f_funke Note Added: 52424
2019-06-17 08:48 DenisChenu Note Added: 52425
2019-06-17 09:49 DenisChenu File Added: Capture d’écran du 2019-06-17 09-44-40.png
2019-06-17 09:49 DenisChenu File Added: Capture d’écran du 2019-06-17 09-44-51.png
2019-06-17 09:49 DenisChenu File Added: Capture d’écran du 2019-06-17 09-48-37.png
2019-06-17 09:49 DenisChenu Note Added: 52426
2019-06-17 09:50 DenisChenu Note Added: 52427
2019-07-11 12:03 cdorin Assigned To => markusfluer
2019-07-11 12:03 cdorin Status new => assigned
2019-07-12 11:08 markusfluer Note Added: 52860
2019-07-12 11:23 DenisChenu Note Added: 52861
2019-07-12 11:25 DenisChenu Note Edited: 52861 View Revisions
2019-07-12 11:25 DenisChenu Note Edited: 52861 View Revisions
2019-07-12 11:39 markusfluer Note Added: 52862
2019-08-05 11:49 f_funke Note Added: 53093
2019-08-05 16:13 markusfluer Note Added: 53109
2019-10-30 19:56 Mazi Note Added: 54286
2019-10-30 20:23 f_funke File Added: grafik.png
2019-10-30 20:23 f_funke Note Added: 54287
2019-10-30 21:53 DenisChenu Note Added: 54288
2019-10-30 23:17 Mazi Severity minor => crash
2019-10-30 23:17 Mazi Note Added: 54292
2019-11-01 09:32 f_funke Note Added: 54305
2019-11-01 09:35 Mazi Note Added: 54306
2020-02-25 08:19 DenisChenu Assigned To markusfluer =>
2020-02-25 08:19 DenisChenu Status assigned => new
2020-02-25 08:19 DenisChenu Relationship added related to 15913
2020-02-25 09:05 Mazi Note Added: 56195