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

Issue 694505 link

Starred by 1 user
Status: WontFix
Owner:
█ jif@chromium.org
Last visit > 30 days ago
Closed: Mar 2017
Cc:
mard...@chromium.org
olivierrobin@chromium.org
ios-bugs@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 3
Type: Bug



Sign in to add a comment

Move the PDF's "Open In..." button to the share menu.

Project Member Reported by jif@chromium.org, Feb 21 2017 
In order to increase the discoverability of the sharing of PDF as well as simplifying the code base, I propose we move the "Open In..." button from the bottom bar that appears when tapping PDFs to the share menu.

In other words, when the user shares a page that is a PDF, the share menu would contain an additional action (called "Share PDF" in the attached screenshot). Pressing that item would trigger the same flow as pressing the "Open In..." button, that is it would open a second share menu that shares the PDF (as opposed to the first share menu that shares a URL).
Screen Shot 2017-02-20 at 11.23.36 AM.png
457 KB View Download

Comment 1 by olivierrobin@chromium.org, Feb 21 2017 

The two actions will be very different.
Imagine a drive (or a drop box) action.
It is legitimate to think that the action appears both in the UIActivityViewController and in the UIDocumentInteractionController

but doing
Share > Drive: will send the URL to drive, and drive will download the file
Share > Open in > Drive will download the file in Chrome and give it to drive.

The two result can be different (e.g. the first can fail if downloading the file requires credentials).
Should we highlight this difference somehow?

Comment 2 by jif@chromium.org, Mar 9 2017

Status: WontFix (was: Assigned)
An other solution was implemented

Comment 3 by mard...@chromium.org, Mar 10 2017 

What's the other solution?

Comment 4 by jif@chromium.org, Mar 10 2017 

Simply display the "Open in..." toolbar by default.
Discussion (and design doc) at: https://bugs.chromium.org/p/chromium/issues/detail?id=688531
►

Sign in to add a comment