Skip to content

Playground has sporadic "already declared" issues. #34

Description

@dmitshur

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).

Activity

  1. dmitshur commented on Oct 18, 2015

    @dmitshur
    MemberAuthor

    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.

  2. dmitshur commented on Jan 17, 2016

    @dmitshur
    MemberAuthor

    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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions