New issue
Advanced search Search tips

Issue 647800 link

Starred by 2 users
Status: Duplicate
Merged: issue 626415
Owner:
einbinder@chromium.org
Closed: Sep 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

I there is an active service worker, console context is set to the service worker by default

Reported by m...@azimi.me, Sep 16 2016 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

Steps to reproduce the problem:
1. got to https://lodash.com/docs/4.15.0
2. open console

What is the expected behavior?
The console context should be "top"

What went wrong?
Console context is the single service worker that is activated instead of top

Did this work before? N/A 

Chrome version: 52.0.2743.116  Channel: n/a
OS Version: OS X 10.11.6
Flash Version: Shockwave Flash 22.0 r0
Screen Shot 2016-09-16 at 1.34.12 PM.png
13.0 KB View Download

Comment 1 by chenwilliam@chromium.org, Sep 16 2016

Owner: l...@chromium.org
Status: Assigned (was: Unconfirmed)
luoe@ IIRC, this issue was recently resolved?

Comment 2 by l...@chromium.org, Sep 16 2016

Mergedinto: 626415
Owner: einbinder@chromium.org
Status: Duplicate (was: Assigned)
Thanks for your report, we've seen similar issues lately 626415, 630084, 613878

einbinder@ has fixes for the execution context selector in Chrome Beta 54.0.2840.27 atm.  They should be arriving on stable in the next release.

Please reply and let us know if you see this behavior on beta/dev/canary.
►

Sign in to add a comment