New issue
Advanced search Search tips

Issue 804119 link

Starred by 1 user
Status: Duplicate
Merged: issue 799312
Owner: ----
Closed: Jan 2018
Cc:
wfh@chromium.org
creis@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Opening gmail or google calendar via chrome://apps or via session restore with strict site isolation enabled results in DOMException

Reported by cerver...@appstate.edu, Jan 20 2018 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce the problem:
1. enable strict site isolation 
2. restart browser
3. click the 'Apps' link in the Chrome favorites bar or go to chrome://apps
4. click gmail

What is the expected behavior?
gmail opens

What went wrong?
gmail hangs on the loading screen and a number of javascript errors are thrown. DOMException blocked a frame from accessing cross-origin frame 

Did this work before? N/A 

Chrome version: 63.0.3239.132  Channel: stable
OS Version: Windows 10
Flash Version: 

Also happens for google calendar. Both result in the error when accessing via the chrome://apps function or when closing and reopening the browser while having gmail and/or calendar open and having the browser restore open tabs. Disabling the site isolation feature restores normal functionality.
Capture.JPG
171 KB View Download

Comment 1 by elawrence@chromium.org, Jan 21 2018

Components: Internals>Sandbox>SiteIsolation
Labels: -Type-Bug-Security -Restrict-View-SecurityTeam FoundIn-63 Type-Bug

Comment 2 by lukasza@chromium.org, Jan 21 2018 

Thank you very much for the bug report!

This sounds very similar to  issue 799312 .  If it is a duplicate, then 1) a workaround would be visiting https://mail.google.com (rather than launching GMail from chrome://apps) and 2) the problem should be resolved in Chrome 64 (which is tentatively planned to be promoted to the stable channel some time next week).

Comment 3 by cerver...@appstate.edu, Jan 21 2018 

Thank you for the response. I agree. It appears to be the same issue. 

We will notify our users of the workaround and update to Chrome 64 upon release.

Have a good day.

Comment 4 by susanjun...@techmahindra.com, Jan 22 2018

Labels: Triaged-ET
Mergedinto: 799312
Status: Duplicate (was: Unconfirmed)
As per comment #2, this issue is similar to  issue 799312  and the reporter has confirmed the same.

Hence merging this issue to  issue 799312 .

Thanks..
►

Sign in to add a comment