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

Issue 611994 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Some platform apps don't show at all (actually, just Calculator)

Project Member Reported by kuscher@chromium.org, May 14 2016

Issue description

Chrome Version       : 52.0.2727.0
OS Version: 8298.0.0

When opening the Calculator platform app, it has no contents whatsoever. (just blank window). 

Inspect says something in foam is broken? kgr?

foam.js:848 Uncaught TypeError: Illegal invocation


 

Comment 1 by kgr@chromium.org, May 14 2016

Cc: miket@chromium.org
Labels: OS-Linux
Owner: kgr@chromium.org
Status: Started (was: Untriaged)
I've verified the exception is thrown in Chrome 52 when run as a Chrome Packaged App, but not in Chrome 51 or in Chrome 52 when run as a regular web-page.

The error appears that our reference to 'document' isn't defined when we first try to use it.

Mike, has anything changed in M52 regarding packaged app startup?

Comment 2 Deleted

Comment 3 by kgr@chromium.org, May 14 2016

I seem to have a fix. I'll need to run through our test plan to verify that we haven't caused any regressions, and then we'll issue an updated release (probably on Monday).

Comment 4 by adamvy@google.com, May 14 2016

I can't repo on Chrome Canary 52.0.2735.0

Comment 5 by adamvy@google.com, May 14 2016

I can repo in Chrome Dev 52.0.2729.3

This seems to only be a problem in Dev

Comment 6 by adamvy@google.com, May 16 2016

I've attached a minimal repo case that triggers this error.

If you build some object who's prototype is window

var obj = Object.create(window);

and then try to access the document.

obj.document.insertAdjacentHTML('beforeend', 'hello');

it throws an Illegal Invocation exception.

This is a regression in Chrome's behaviour.  Where would be the right component to report this to?


I'm also pushing a new calculator version that works around this issue, but it would be good to fix the chrome regression also.
repoapp.zip
1.2 KB Download

Comment 7 by miket@chromium.org, May 16 2016

Cc: -miket@chromium.org

Comment 8 by miket@chromium.org, May 16 2016

Cc: asargent@chromium.org

Comment 9 by kgr@chromium.org, May 16 2016

Status: Verified (was: Started)
Fixed and verified.

Comment 10 by adamvy@google.com, May 16 2016

I filed https://bugs.chromium.org/p/chromium/issues/detail?id=612192 to track the chrome regression.

It has shorter repo steps.

Sign in to add a comment