New issue
Advanced search Search tips

Issue 772678 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome extension event page redirecting to data:text/html,chromewebdata immediately after execution

Reported by chronomo...@gmail.com, Oct 7 2017

Issue description

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

Steps to reproduce the problem:
1. Download and install extension in dev mode
2. Set background page console to Preserve log
3. reload extension
4. Console log will show navigated to to data:text/html,chromewebdata.
5. Background page disappears from Chrome Developer page

What is the expected behavior?
Event page should remain active after processing background script (reloading extension)

What went wrong?
It appears the thresh hold for processing time before the event page disappears has been changed. Now when load my extension, the code runs but then immediately the console logs "Navigated to data:text/html,chromewebdata" and the background page will visibly disappear from chrome://extensions. Callbacks are not completed before this happens

Did this work before? Yes Yesterday

Chrome version: 61.0.3163.100  Channel: stable
OS Version: OS X 10.12.6
Flash Version: 

If preserve log, console says "Navigated to data:text/html,chromewebdata" which seems to be stopping the background page from executing the remainder of the code.

Extension is current test build of preexisting extension 

Test Extension can be downloaded via https://drive.google.com/open?id=0B_L8uG1d0i54aS12RExKLXktb0E

Screen recording: https://drive.google.com/open?id=0B_L8uG1d0i54aE9RSGsyRnVsTDg
 
Also objects do not expand when click the "open" triangle
Screen Shot 2017-10-07 at 7.01.05 PM.png
28.0 KB View Download

Comment 2 by woxxom@gmail.com, Oct 7 2017

You have a bug in your code:

var type = object['type'];
        zone = object['time']['zone'];
        offset = object['offset'];
        location = object['location'];

As you can see, instead of commas you've used semicolons so "location = object['location'];" became a separate statement which assign to a global "location" (effectively "window.location") thus navigating to the assigned value.
Thanks for the help, woxxom!
Labels: Needs-Triage-M61

Comment 5 by alph@chromium.org, Oct 9 2017

Status: WontFix (was: Unconfirmed)
Closing as not a bug per comment #2. Thanks Woxxom!

Sign in to add a comment