Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.


Color does not show when the cursor is over color name

I have never used workspace before, but I find minor irritation that when I hover my cursor over the color name the color does not show up for me like it does on the instructors screen.

I am using Firefox on Windows 7.

Has this happened for anyone else? My main concern is that when I get further into the program there will be more small issues such as this one that slows down the process as I get distracted trying to trouble shoot.

2 Answers

Tim Knight
Tim Knight
28,888 Points

Hi Johanna,

I tested this out from a Mac and I discovered that it doesn't work for me within Firefox either. It only seems to work in Chrome and Safari.

Thanks Tim! Silly firefox. Good to know it is not just my computer being spazzy, but rather is at the fault of the browser.

Charles Smith
Charles Smith
7,575 Points

This doesn't solve the problem exactly, but try http://www.w3schools.com/tags/ref_colorpicker.asp

Enter the hex into the box, click submit, and you should be able to see what color they are talking about in the video. Also, this is a fantastic resource when doing design on your own. Makes it very easy to find the color your looking for (and the hex you need for your CSS).

I had previously used color picker and color indexes. I just really wanted to see the colors pop up when I put my cursor over them. Fortunately Tim resolved my issue by informing me it was just Firefox. I opened the website up on Chrome and it worked just fine :)