tel: links are broken on ChromeOS
Reported by
spuddybu...@gmail.com,
Apr 17 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 9334.42.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.68 Safari/537.36 Platform: 9334.42.0 (Official Build) beta-channel samus Example URL: https://developers.google.com/web/fundamentals/native-hardware/click-to-call/ Steps to reproduce the problem: 1. Click on number that demonstrates tel: functionality. 2. A dialog pops up saying "Chrome OS can't open this page." What is the expected behavior? Chrome allows me to set Hangouts/Google Voice as the external protocol handler. What went wrong? Chrome OS has no way of setting external protocol handlers for phone numbers, contradicting Google's own advice for enabling this functionality. Does it occur on multiple sites: Yes Is it a problem with a plugin? N/A Did this work before? N/A Does this work in other browsers? N/A Chrome version: 58.0.3029.68 Channel: beta OS Version: 9334.42.0 Flash Version:
,
Apr 19 2017
+benwells, do I remember hearing you say that you worked on protocol handlers once upon a time? Do you know who maintains this now?
,
Apr 19 2017
Yes ... I probably did say that. There are two different ways this could be solved: - ChromeOS provides some hard coded mapping for tel: links - Sites that can handle tel: links add registerProtocolHandler: calls to handle it Bumping to the ChromeOS team to triage. I'm not sure what component this should have but it isn't Blink.
,
Apr 19 2017
I browsed to https://hangouts.google.com and https://www.google.com/voice and neither offered to register a protocol handler that I could see (no double diamond icon in the omnibox). I'm happy to file a FR against either of those, but note: currently outbound PSTN for me is handled not by hangouts.google.com, but by the Hangouts Chrome app. Can an app register protocol handlers on install?
,
Apr 19 2017
This should be handled by registerProtocolHandler for tel:. Filing a FR against the webapps is probably the way forward here.
,
Jun 19 2017
,
Sep 10 2017
WontFixing since this should be handled by the webapp itself rather than by Chrome. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by mfo...@chromium.org
, Apr 17 2017