Preview from Drive fails to load pages with links on Chrome Browser for iOS |
|||||||||||||||
Issue descriptionChrome Version: 57.0.2987.137 OS: iPhone6s plus iOS 10.3.1 iPhone 6 iOS 10.2.1 iPad Mini 10.2.1 iPhone 5SE 10.3.1 What steps will reproduce the problem? 1. Create a PDF file that contains an edited link (not a raw www.google.com line but have a text to display pointing to a link) 2. Upload the PDF to drive.google.com 3. On the iPhone, open Chrome browser and access drive.google.com 4. Open the PDF file > Only the page containing the "edited link" shows an loading error. What is the expected result? PDF file displayed correctly, without Whoops pages What happens instead? All pages shown correctly except for the page containing the "edited link", which shows an loading Whoops error. Attached sample file, which was used to reproduce an error. Same behavior seen with Google Drive Getting Started PDF file, though not sure if the same bug (it would only show first page).
,
Apr 10 2017
Even though this involves a PDF, Internals>Plugins>PDF is not the right component because Chrome on iOS does not use the desktop PDF plugin.
,
Apr 11 2017
Why was this bug assigned to me? I see no reason and am unassigning myself. CC me if you feel otherwise.
,
Apr 12 2017
,
Apr 12 2017
,
Apr 17 2017
Hi there! Is there any update on this? Thank you!
,
Apr 17 2017
This does not repro in Safari or WKWebView. It does repro in web shell and Chrome iOS. I am wondering if Docs does something different for the Chrome iOS user agent, since I generally would not expect browser code to interact with Drive's custom PDF viewer. Did you also file a bug with them? Eugenebut, any ideas come to mind?
,
Apr 18 2017
We can try testing with Safari User Agent, which can be set via experimental settings.
,
Apr 18 2017
I tested this with the Safari user agent, and it did not repro. So, it is a bug on the Drive side.
,
Apr 18 2017
Does Drive know about this bug? If this is a drive bug, then we should file bug against Drive and close this as ExternalDependency.
,
Apr 18 2017
vkhabarov: Have you already reported this bug to Drive?
,
Apr 20 2017
gchatz: No, I didn't, I'm on Chrome support, not sure what is the correct way to file a Drive bug or if I have necessary access.
,
May 10 2017
gchatz@, could you please file a bug agains Drive. Thanks!
,
May 31 2017
Filed.
,
May 31 2017
ghatz@, what is the bug number, so we can track it?
,
May 31 2017
,
Jun 5 2017
vkhabarov: Are you still able to repro this? I am not able to anymore, and the drive team was not able to either.
,
Jun 6 2017
gchatz: No, can't repro. Seems to be fixed.
,
Jun 6 2017
Marking as Won'tFix since can't repro. |
|||||||||||||||
►
Sign in to add a comment |
|||||||||||||||
Comment 1 by vkhabarov@chromium.org
, Apr 10 2017