Issue metadata
Sign in to add a comment
|
Can not "print" PDF to Cloud drive
Reported by
tywi...@gmail.com,
May 16 2016
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 7978.66.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.91 Safari/537.36 Platform: 7978.66.0 (Official Build) stable-channel falco Steps to reproduce the problem: 1. Go to print 2. Save as PDF What is the expected behavior? Allow to save to drive What went wrong? Only save to download WebStore page: Did this work before? Yes Chrome version: 50.0.2661.91 Channel: n/a OS Version: 7978.66.0 Flash Version: Shockwave Flash 21.0 r0
,
May 16 2016
Yes I can access Google Drive. I've tested with two accounts. It worked before and might have broken after the 50 update.
,
May 16 2016
When you get to the "Save As" dialog: 1) What do you see in the left pane? For me, I see: Google Drive - My Drive Downloads 2) Assuming you see "My Drive" - can you select it? For me, the answer is yes. 3) Assuming you can select it, if you hit the "Save" button, what happens next? For me, I successfully saved to Google Drive. Testeed with Chrome 51 beta channel here. I can find another Chromebook and test with Chrome 50.
,
May 16 2016
I can "save" to Drive but not "print" to it. Normally after clicking print and then selecting "save as PDF" and click save, I believe you could save to Drive.
,
May 16 2016
If you can't, could I request that you could?
,
May 16 2016
re: comment 4 - in comment 3, I tried to explain to you what's happening for me when I print -> save as pdf -> get the save as dialog. You repeatedly said this does not work for you, but I don't understand what's going wrong for you. If you can better describe what you see, or attach some screenshots, that would be helpful.
,
May 16 2016
See attachments
,
May 16 2016
Thanks. The screenshots are helpful. I'm not sure why only "Downloads" appear when you are saving to PDF. I'll go find another Chromebook to test with.
,
May 16 2016
I tried a falco device running Chrome 50 like yours and it behaves just like your device. However, my other device with Chrome 51 works fine, so I'm guessing it could be that your bug was recently fixed in another bug, and all you have to do is wait for your device to update to Chrome 51 in a few weeks.
,
May 17 2016
This seems to have been fixed by Issue #595503
,
May 17 2016
re: comment 10 - thanks, I knew there was a duplicate bug somewhere. Looks like Chrome 50.0.2661.104 will have the update, so any day now rather than in a few weeks.
,
May 17 2016
I'm now on 50.0.2661.103 and it's still broken.
,
May 17 2016
You need 50.0.2661.104. It should roll out shortly.
,
May 17 2016
Ah cool. I thought you had a typo. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by thestig@chromium.org
, May 16 2016