# Bad colours on/in browser

**URL:** <https://discourse.nodered.org/t/bad-colours-on-in-browser/57176>\
**Category:** General\
**Created:** [24 January 2022 21:29 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176 "2022-01-24T21:29:05Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [24 January 2022 21:29 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176/1 "2022-01-24T21:29:05Z")

</div>

Quick back story:  
I use FireFox. Run Ubuntu 20.04

A long time ago when entering my password a colour requester popped up (unexpectedly) and I have had this little problem since - I think.

Sometimes when reading things the colour _contrast_ is wrong and I can hardly read what is written.

People in/on the Firefox forum have helped me with SOME of the problems.  
Though I can't say I am 100% sure, but the result does look better from what I remember it being.

But the underlying problem remains.

Without wanting to start a finger pointing game, here's what I know.  
In FireFox some things are near impossible to read.

Example:  
I was wanting to use the cronplus node and was looking at the instructions.

 ![Screenshot from 2022-01-25 06-50-13](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/4/345656d841a1761d467d08de520a2fe0aa2dd4c6.png)

As you can see the big white rectangle on the right is near impossible to read.

I tried using "PRIVATE" mode... No change.

Today I even tried Opera....

 ![Screenshot from 2022-01-25 08-22-35](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/0/503144776c9909aa7cd534b4ef0429db7e074f3a.png)

Same. So it can't be a FireFox problem.

Does anyone else see this?  
(Probably not)

But I am lost in what to do so I can read these kind of pages.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [24 January 2022 21:31 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176/2 "2022-01-24T21:31:51Z")

</div>

Have you checked what css class that element has? I suspect that it hasn't been styled though you are obviously using a dark mode theme.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [24 January 2022 21:31 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176/3 "2022-01-24T21:31:53Z")

</div>

What theme are you using & what version of cron plus?

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [24 January 2022 21:34 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176/4 "2022-01-24T21:34:14Z")

</div>

@TotallyInformation No. Sorry, I don't even understand the question.

@Steve-Mcl 1.5.4

It isn't I am saying it is unique to that node.

It is just I was reading the instructions today and saw it happening on that node.

I can check other nodes too if needed. But that may be a slow process.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [24 January 2022 21:35 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176/5 "2022-01-24T21:35:15Z")

</div>

> [@Trying\_to\_learn](#):
>
> It isn't I am saying it is unique to that node

No, i know, however i recently fixed some rubbish CSS overrides in cron-plus. You can try V1.5.6 in the flow lib

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [24 January 2022 21:37 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176/6 "2022-01-24T21:37:58Z")

</div>

> [@Trying\_to\_learn](#):
>
> Sorry, I don't even understand the question.

You are using a dark mode theme are you not? There are likely some elements of Node-RED where the theme hasn't applied a style or possible where Node-RED still has manual styling so that the theme can't style it. The other possible issue - as Steve says - is that perhaps some nodes have applied manual styling themselves and so the theme is ignored there.

You or someone else would need to look at the mis-styled elements using the browser dev tools to find out which of these issues applies.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [24 January 2022 21:39 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176/7 "2022-01-24T21:39:47Z")

</div>

Hmmm...

I could see there was an update.  
Went to the palette manager and upated.

"You need to restart node-red....."

Done.

Load the manager... Still saying 1.5.5

 ![Screenshot from 2022-01-25 08-37-45](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/5/55f8f4eba568449fe12c66a0edc5916d39cbe251.png)

 ![Screenshot from 2022-01-25 08-38-56](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/5/d57b2643f89be7b4e2ac83a858f48c60d430676e.png)

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [24 January 2022 21:40 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176/8 "2022-01-24T21:40:54Z")

</div>

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/d/7dd63cb5cace30a051d67644b74105c441013a57.png)

1.5.6 was posted about 10 mins ago

Refresh your browser

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [24 January 2022 21:41 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176/9 "2022-01-24T21:41:42Z")

</div>

Sorry.... Ok.

Dev tools.... eeeeech.... That is a whole different world to me.

I have very little understanding on how to use that stuff.

I guess - offering - would it be an idea to disable the dark theme and try again - sorry I didn't think of this before.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [24 January 2022 21:43 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176/10 "2022-01-24T21:43:17Z")

</div>

When I looked at the palette manager the first time it said 1.5.6 was there.

I updated it and was told I had to restart NR.

Stopped it and started it - as per screen shot.

When I went back into NR, it was saying it was version 1.5.5.

I did a SHIFT REFRESH on the page. Same.  
(shift refresh - AFAIK that wipes the cache.)

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [24 January 2022 21:43 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176/11 "2022-01-24T21:43:32Z")

</div>

> [@Trying\_to\_learn](#):
>
> I guess - offering - would it be an idea to disable the dark theme and try again

If you are using "midnight-red" you might need to update that.

Also, I seem to remember that shading issue you have was fixed in newer node-red  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/b/db2995c1a39a86cdfa3ca1de74b2b40a4c2e5d93.png)

So you likely need to update to latest node-red

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [24 January 2022 21:45 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176/12 "2022-01-24T21:45:17Z")

</div>

I've got NR 2.1.4 now.

I'll check if there are updates to the midnight-red theme.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [24 January 2022 21:48 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176/13 "2022-01-24T21:48:10Z")

</div>

(sorry....)  
When doing the installing of that theme (looking at page now)  
the command to install is to be run from the `.node-red` directory - yeah?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [24 January 2022 21:56 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176/14 "2022-01-24T21:56:50Z")

</div>

> [@Trying\_to\_learn](#):
>
> to install is to be run from the `.node-red` directory - yeah?

From memory - yes.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [24 January 2022 22:01 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176/15 "2022-01-24T22:01:04Z")

</div>

After a bit of messing around, I simply disabled it to get a base line.

(Though I should try to remember which part isn't readable.)  
(But if it isn't readable... how do I know which part?) 😉

Just checked... OK, it was the `dawn` bit... But anyway.

 ![Screenshot from 2022-01-25 08-57-44](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/8/58ada17d3baefeaf6bc756dfc9d58ee3f19a0611.png)

Seems it is the theme which is not liking it.  
Sorry.

I'll maybe ask if anything can be done at that end of things.

Just the dark theme is less stressful on my eyes.

When I use other programs with WHITE background, I nearly have to wear sunnies to look at the screen. 😉

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [24 January 2022 22:03 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176/16 "2022-01-24T22:03:08Z")

</div>

> [@Trying\_to\_learn](#):
>
> shift refresh - AFAIK that wipes the cache

Nope. You have to do it via the menus.  
In FF that is Settings \> Privacy & Security \> History section - Clear History \> select Cache and Offline web site data - OK

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [24 January 2022 22:05 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176/17 "2022-01-24T22:05:14Z")

</div>

Sorry, I'll rephrase that.

Simply pressing REFRECH .. refreshes the page.

If things have changed at the remote end they may not be shown.

Pressing SHIFT REFRESH forces the browser to reload the entire page.

Better?  
Or am I still wrong?

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [24 January 2022 22:09 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176/18 "2022-01-24T22:09:51Z")

</div>

> [@Trying\_to\_learn](#):
>
> I have very little understanding on how to use that stuff.

Ah well, life is full of choices 🙂 Live or learn?

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [24 January 2022 22:21 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176/19 "2022-01-24T22:21:53Z")

</div>

Got `cronplus` updated to `1.5.6`. Still happening.

Don't worry. It seems it is only that node.  
I did a quick check and couldn't find any other node with the problem.

Not the end of the world.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [24 January 2022 22:21 UTC](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176/20 "2022-01-24T22:21:56Z")

</div>

> [@Trying\_to\_learn](#):
>
> Pressing SHIFT REFRESH forces the browser to reload the entire page.
> 
> Better?  
> Or am I still wrong?

It does not force it to reload absolutely everything. To be certain you have to go through the menus. I thought like you once, then the dashboard was misbehaving after an upgrade. Dave (I think) said basically what I have just written and he was correct. Forcing a cache clear through the menus fixed it.

[Next page](https://discourse.nodered.org/t/bad-colours-on-in-browser/57176.md?page=2)