Dark theme causes Silence options to show Blank options

[Shahjaved]

When using White theme (Default theme) you are able to see the TEXT in the Silence/Unsilence options.

Current Behavior

When using "Dark" theme you are NOT able to see the TEXT in the Silence/Unsilence options.
Expected Behavior - Should be able to see TEXT in Silence/Unsilence options.

Possible Solution

Text color should change to White when selecting the Dark Theme

Steps to Reproduce (for bugs)

1. Change Theme to "Dark" Theme
2. Go to Alerts, select alerts to silence.
3. Choose the text in Silence/Unsilence Options.
   4.Unable to see text until you mouse over and highlight the options in the drop down.

Context

Unable to see Text using Dark theme. We only use Dark theme and now are hindered in using it.

Your Environment

• Uchiwa version used: 1.1.3-2
• Sensu version used: 1.2.1-2
• Operating System and version: CentOS release 6.7

[palourde]

Hi @Shahjaved,

Thank you for reporting this issue. Unfortunately I was unable to reproduce with Chrome or Firefox.

Chrome 64:

Firefox 58:

Can you let us know which browser and version you are using? Also, were you able to reproduce that problem on a different machine and/or browser?

Thanks

[exeral]

Hello, I confirm

Linux Fedora 27
Google Chrome
Version 64.0.3282.167 (Build officiel) (64 bits)

Uchiwa 0.26.3

[palourde]

So far the only common thing I see if that you both are running Linux. I don't have access to a linux machine with a GUI right now, so I'll need to setup something.

[Shahjaved]

@palourde Sorry for the delayed response, i was on vacation and forgot about this.
The browser i was using is Chrome - Version 65.0.3325.181 (Official Build) (64-bit)

I tried reproducing on IE and FireFox. Firefox showed a white background still but i was able to see black text just fine (kind of ugly though but usable).

Firefox - 57.0.2 (64-bit) - Able to see text but has white background

Internet Explorer is giving me a completely different issue where it won't even show the menu for silencing, so we'll leave that out of this specific Bug.

[palourde]

@Shahjaved I was finally able to reproduce that issue on Microsoft Edge 41 and submitted a PR for this issue. Hopefully it will be solved for all browser/operating systems concerned.