1. Forum
  2. >
  3. Topic: Troubleshooting
  4. >
  5. Priority low but Red hurts my…

https://www.duolingo.com/profile/velvelajade

Priority low but Red hurts my eyes and is blurry.

Is there anyway that you can make it so that we can choose what color our status bars will show across the top? Or at least, just have basic blue for those of us who has the colour blindness or sensitivity issue where red is a blur? Thanks!

March 12, 2015

5 Comments


https://www.duolingo.com/profile/psionpete

You can create your own user cascade style sheet (CSS) and save it on your local disc. If you cannot do this, a friendly web designer should be able to do it for you.

Once installed, your styles will override styles contained in web pages etc. so you could prevent Red being used anywhere on a web page.

March 12, 2015

https://www.duolingo.com/profile/velvelajade

My CSS "won't" override web pages as their pages won't call my CSS page, and can't call it from my desktop. You need to know what they are calling everything in their own CSS so that your CSS uses the same names. And, when I tried using Firefox's chose your background colour and font colour, I would get black background with black text because some sites banned my font colour choice (on forms especially). Granted, I've not tried this in several years, so maybe now a days, its better.

With that in mind, What method specifically, with all the steps would you use to get them to use my CSS sheet? I'm using Chrome now. Did they come up with something new that actually works? Thanks!

March 13, 2015

https://www.duolingo.com/profile/psionpete

It is a few years ago that I used CSS but it was certainly possible in CSS2 and there is probably a newer release now.

To use your own CSS file, you need to tell your browser where it is and then it is included in the normal CSS heirarchy, unfortunately each browser is different about where this is. I think in Mozilla, your rules are added to the user.css file but this may have changed. Not sure where it is in Chrome.

Also You cannot use any selectors that presume specific attribute values such as class or id because you will not know what is in the html of each page. You also need to add !important to each rule to give them highest priority and to ensure that it will overide the authors !important rules. Other than that you can use most of the CSS rules.

March 13, 2015

https://www.duolingo.com/profile/velvelajade

Doh! I completely forgot that !important now works consistently. There was another thing "@NameOfFileHere" that would mostly not work even though Firefox supported it back in the HTML 4 days. It may have had something to do with the OS, as I can't remember if I was on an old ancient Mac, or the XP. lol

I also forgot that Firefox had that user.css that was years better than their silly Options form that didn't work for Forms on webpages.

I'll have to find it in Chrome. I'll google it.

The Link I found: http://stackoverflow.com/questions/21207474/custom-css-has-stopped-working-in-32-0-1700-76-m-google-chrome-update

The other link I found was to code google, and because that is going away, I decided to not post that link. But anyway. I hope this helps someone. However, it is looking like using Firefox may be the better choice as its just easier. I might just live with the red and try not to look at it too much.

March 14, 2015

https://www.duolingo.com/profile/Lrtward

"You need to know what they are calling everything in their own CSS so that your CSS uses the same names."

In Chrome, just right-click the element in question and then "Inspect Element". Mozilla used to use an add-on or plug-in called Firebug that did this but I think now they support the "Inspect Element" as well. Mine does, but I can't recall if that's native or due to an plug-in.

March 13, 2015
Learn a language in just 5 minutes a day. For free.