Blocking custom schemes creates a usability conundrum for users
||Date Originated:||14-Dec-2016 12:25 PM|
||Product Version:||Version 10.0.2 (12602.3.12.0.1)|
Starting in macOS 10.12.2, Safari is more active about preventing custom schemes from launching pertinent applications. This applies not only to custom schemes invoked from web content, but also from user-installed Bookmark Bar links.
Bookmarklets are sometimes used to facilitate an ease of workflow between the web and native apps. My app, MarsEdit, offers such a bookmarklet to users, so that they can easily open a new blog post draft based on the current page and selected content in Safari.
The particular workflow accommodated by this is stymied by having to repeatedly confront a permissions panel in Safari, every time the bookmarklet is used.
It would be good if there were some way of whitelisting schemes or, better yet, providing an option to users to "Always Allow" opening a particular application.
The argument for allowing users to open specific applications is greater for bookmarklets, because the user is likely to have manually installed the bookmarklet in order to accommodate a certain workflow.
Steps to Reproduce:
1. Download MarsEdit:
2. Launch the app (you can skip configuring a blog).
3. Select MarsEdit -> Install Browser Bookmarklet from the menu bar at the top of the screen.
4. Drag the "Send to MarsEdit" link from the page in Safari, to the Bookmark Bar.
5. Navigate to any page on the web.
6. Click the "Send to MarsEdit" bookmarklet.
If you don't want to download the app, just put this bookmarklet code in a bookmarklet:
Some means of suppressing the warning panel being displayed every single time.
The user must click through the tedious panel in order to complete the action.
Version 10.0.2 (12602.3.12.0.1)
Reports posted here will not necessarily be seen by Apple.
All problems should be submitted at bugreport.apple.com before they are posted here.
Please only post information for Radars that you have filed yourself, and please do
not include Apple confidential information in your posts. Thank you!