Issue metadata
Sign in to add a comment
|
Settings does not expose external protocol handlers
Reported by
cesar.lz...@gmail.com,
Sep 8 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Steps to reproduce the problem: 1. Open a telnet:// extension 2. Choose a special application as preferred for telnet urls like putty. 3. There is no way to modify this preference. Handler list is empty What is the expected behavior? To have a way to revert this option or to change the application used. What went wrong? Unable to change the application even if it has been uninstalled. Did this work before? N/A Chrome version: 52.0.2743.116 Channel: n/a OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 22.0 r0
,
Sep 14 2016
I think this is a deficiency of the Settings UI. That state is stored in the profile, but not surfaced through the UI :\ Over to dbeam@ for settings triage or routing.
,
Jul 6 2017
I'm no longer working on Chrome, and unlikely to fix any bug I'm currently assigned. So this bug doesn't languish, I'm unassigning myself.
,
Feb 13 2018
,
Feb 13 2018
@aee: Can you triage this bug? Is this the same as issue 744717 or is it a separate issue?
,
Feb 14 2018
dpapad@, I'm still digging into this. my initial findings is that it is a separate issue. In linux, a telnet link would fallback to `xdg-open`. A user can then configure how a URL scheme is handled with `xdg-mime`. It's similarly possible to do so for OS X using RCDefaultApp. I am not endorsing this application. It is the first way I found that I could configure how url schemes are handled by the system. I'll report back if I find a more direct way to update the system url scheme handler using a built-in app or cli.
,
Feb 14 2018
IIUC this is a feature request and not a regression then. Found quite a few other bugs in the database related to external protocol handlers, for example see issue 589000. Not sure if there is anything to do about this now, I suggest leaving this Untriaged so that it can be triaged along with other related bugs.
,
Mar 8 2018
,
Mar 8 2018
,
Mar 12 2018
[mac triage] this doesn't belong in mac [UI] triage.
,
Apr 13 2018
,
Apr 13 2018
+chrome/browser/external_protocol/OWNERS
,
Apr 16 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by tkonch...@chromium.org
, Sep 8 2016