W3C home > Mailing lists > Public > public-html-admin@w3.org > January 2013

[Bug 20799] New: launchURI method proposal

From: <bugzilla@jessica.w3.org>
Date: Tue, 29 Jan 2013 05:15:46 +0000
To: public-html-admin@w3.org
Message-ID: <bug-20799-2495@http.www.w3.org/Bugs/Public/>

            Bug ID: 20799
           Summary: launchURI method proposal
    Classification: Unclassified
           Product: HTML WG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec
          Assignee: dave.null@w3.org
          Reporter: adrianba@microsoft.com
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-admin@w3.org,

Many platforms support applications registering as custom protocol scheme
handlers. For example, mailto: is a scheme for mail but often application
platforms encourage app-specific schemes for deep-linking within applications.

While it is undesirable to allow web pages to enumerate the available scheme
handlers or even probe for their support, we have found it useful for an pages
to attempt to navigate to a URI and understand whether it succeeded or failed.
This allows pages to either prompt to install the application or to fallback to
a, potentially lesser, web-based experience.

In IE10, we implemented launchURI with a vendor prefix to accomplish this and
we are interested to know if other vendors might consider supporting this kind
of mechanism in their platform. For simplicity we provided callback methods for
success and failure but obviously an alternative approach could use an instance
object and events.

partial interface Navigator {
  void launchUri(DOMString uri, optional LaunchURICallback successCallback,
optional LaunchURICallback noHandlerCallback);
callback void LaunchURICallback();

This is documented further here:

You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 29 January 2013 05:15:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:57:21 UTC