Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

CSS How to Make a Website Customizing Colors and Fonts Organize CSS with Comments

Why when I type in my /* */ comment code it doesn't take affect within workspace?

Why doesnt my /* */ "comment" code take effect within workspace? It does not comment my code as it should. It doesn't do anything at all..Is this a glitch?

Hey Reggie!

Can you post some code for how you're trying to comment your CSS?

1 Answer

I've had a few instances where when I commented out using that method, the color of the text didn't change. It remained black. Only recently have I seen it go to a gray color. But if you preview your html document, the commented text shouldn't show up.

I've noticed on my version of Workspaces, the colors don't always reflect what the instructor's Workspace screen shows.

I've had a few instances where when I commented out using that method, the color of the text didn't change. It remained black. Only recently have I seen it go to a gray color. But if you preview your html document, the commented text shouldn't show up.

We've definitely been hearing this from students, hopefully all the kinks are worked out for now. If you run into any specific instances where this happens please post some code examples here on the forums so we can take a look.

I've noticed on my version of Workspaces, the colors don't always reflect what the instructor's Workspace screen shows.

This can certainly be the case sometimes. We're constantly working to improve workspaces and that can, in a few cases, include changes to the syntax highlighting. While we try to go back and reshoot these segments it's an ever increasing task as we add more content to the library. Hopefully this hasn't caused too much confusion.