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

JavaScript JavaScript Loops, Arrays and Objects Simplify Repetitive Tasks with Loops The Refactor Challenge

Problem launching WorkSpaces in videos

Since the 'update' I've noticed that when I launch the workspaces in some videos the main window resets to something that says 'related' workspace while also popping up in the workspace window as well.

Firefox 36.0 Mac OS 10.10.2

It's rather annoying - since the back button goes to the link BEFORE the video and then the 'relaunch' option doesn't always work well

3 Answers

I also use google chrome and I have this issue, the only way I can see to stop it from happening is by cancelling the process (by pressing the X that replaces the refresh button when the page is loading). This will keep you on the same page and won't even stop the video.

Hope that makes sense!

Hi John,

I've noticed the same issue and found success with Google Chrome. It's not a perfect solution but generally solves the problem.

Happy learning!

Gina Russo
Gina Russo
8,742 Points

Yes, Google Chrome works for me. I kept getting a timeout message when launching workspace in firefox.

I'm aware how to stop the issue - the problem is that it's a bug in the system that I was trying to notify treehouse about...it needs to be trouble shot.

In that case I would reccomend going to this page: http://teamtreehouse.com/support and reporting it as a bug :)

Saying that it hasn't happened to me in a while now, so maybe it has already been fixed?