New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 635522 link

Starred by 5 users

Issue metadata

Status: Duplicate
Merged: issue 635928
Owner:
Last visit > 30 days ago
Closed: Aug 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Console global context resets randomly

Reported by ja...@goldfirestudios.com, Aug 8 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.82 Safari/537.36

Steps to reproduce the problem:
1. Open console at https://howlerjs.com/ (it isn't dependent on website, just an example of where I'v been seeing it).
2. Type the global Howler variable into the console and hit enter.
3. Sometimes an error is returned: Uncaught ReferenceError: Howler is not defined. Sometimes it will happen immediately after loading into the page, other times it can take several minutes or longer, and still other times it never happens.

What is the expected behavior?
These global variables are actually defined and still work in the page itself.

What went wrong?
The only issue is that the console can't access the variables. If you look at the window object it has been completely reset, but all of the code in the page continues to work correctly.

Did this work before? Yes Before Chrome 51

Chrome version: 52.0.2743.82  Channel: stable
OS Version: OS X 10.11.5
Flash Version: Shockwave Flash 22.0 r0
 
Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Unconfirmed)
Thanks for report!
During evaluation console just get input string and evaluate this string in context of page. Maybe you could provide some steps that can help to reproduce this behavior?
Okay, so I've been doing more testing trying to find repeatable steps and I noticed something that hadn't occurred to me before. The issue is happening because the context in the console is switching from 'top' to the context of one of the extensions. However, this isn't an issue with any particular extension because the problem still happens in incognito, the extension that it switches the context to each time is different, and the problem happens on 2 other computers with completely different extensions. I'm still not sure what triggers this, sometimes as soon as you load into the page it is already off of the 'top' context, but it seems very random.
Mergedinto: 635928
Status: Duplicate (was: Assigned)
Thanks! This information is super useful.

Sign in to add a comment