Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Playground has sporadic "already declared" issues. #34

Open
dmitshur opened this issue Oct 5, 2015 · 2 comments
Open

Playground has sporadic "already declared" issues. #34

dmitshur opened this issue Oct 5, 2015 · 2 comments

Comments

@dmitshur
Copy link
Member

dmitshur commented Oct 5, 2015

This may or may not be related to the errors that sometimes happen if you press "Run" too fast while the playground is still loading.

Under some conditions, when refreshing and/or navigating between snippets, I can see these errors pop up in the console:

image

image

The playground still works and executes the entered code, despite those errors. But we should fix them.

I've been able to reproduce this both in latest stable channel of Chrome (45.0.2454.101), and canary version of Chrome (47.0.2526.0).

@dmitshur
Copy link
Member Author

This appears to be related to #27. It's not as bad as it was before, but it's the same type of error happening.

@dmitshur
Copy link
Member Author

I am still seeing this occur occasionally.

It seems to happen most often if you do a hard refresh (clearing all cache) and press Run very quickly after the page is still loading.

image

I don't think it happens if you wait at least 3-4 seconds after refreshing and pressing the Run button.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant