Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 1 user
Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jan 2014
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Compat



Sign in to add a comment
Canary build breaks Google Drive offline mode
Reported by kenny.st...@gmail.com, Jan 3 2014 Back to list
UserAgent: Mozilla/5.0 (X11; CrOS x86_64 5183.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1767.1 Safari/537.36
Platform: 5183.0.0 (Official Build) canary-channel peppy

Example URL:
https://drive.google.com/#offline

Steps to reproduce the problem:
1. Browse to https://drive.google.com/#offline
2. Attempt to enable the offline mode by clicking the button

What is the expected behavior?
The offline mode should proceed to the sync stage after the button is clicked.

What went wrong?
There appears to be an abrupt change (or coding error) in the same-origin policy between docs.google.com and drive.google.com that is breaking the ability for documents to sync offline, as per the below two screenshots.

Does it occur on multiple sites: No

Is it a problem with a plugin? No 

Did this work before? Yes On Chrome 33 Dev, prior to my discovery of the Canary build (which I updated to for this very reason: squashing bugs like this so they don't precipitate down to the more stable channels).

Does this work in other browsers? Yes 

Chrome version: 34.0.1767.1  Channel: canary
OS Version: 5183.0.0
Flash Version: Shockwave Flash 12.0 r0
 
Screenshot 2014-01-03 at 10.17.06.png
351 KB View Download
Screenshot 2014-01-03 at 10.19.54.png
964 KB View Download
Labels: Cr-Platform-Apps-FileManager-Drive
Labels: -Cr-Platform-Apps-FileManager-Drive
Owner: ajaysurie@google.com
Status: Assigned
+ajaysurie (Drive app side)

I don't think file manager is involved here.
I can't reproduce this with 34.0.1772.0. 

Is this still happening?
Okay, apparently with 34.0.1227.1:5205.0.0, it's actually working. Must have been fixed by the Drive team...
Status: WontFix
Sign in to add a comment