W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2013

Re: Allow javascript: URIs for registerProtocolHandler

From: Anne van Kesteren <annevk@annevk.nl>
Date: Wed, 18 Sep 2013 08:01:50 -0400
Message-ID: <CADnb78guSptNV8Qb9=oet7q+LfARkQdvSsObKMd70sceLyS+-Q@mail.gmail.com>
To: "piranna@gmail.com" <piranna@gmail.com>, Ian Hickson <ian@hixie.ch>
Cc: WebApps WG <public-webapps@w3.org>
On Tue, Sep 17, 2013 at 4:34 PM, piranna@gmail.com <piranna@gmail.com> wrote:
> Really :-) I though the same, but since its a "GET equivalent operation"
> just like XHR and in fact Google Charts creates on-demand graphics based on
> the data on the URL query, so why not? So I created a custom fake protocol,
> set it inside the <img> tag and after registering and removing the fake
> protocol several times, I saw it only showed the image using the fake
> protocol when it was registered :-)

This section does not define how the pages registered by these methods
are used, beyond the requirements on how to process the url value (see
above). To some extent, the processing model for navigating across
documents defines some cases where these methods are relevant, but in
general UAs may use this information wherever they would otherwise
consider handing content to native plugins or helper applications.

Ian, was it ever the intent that these methods affect the way Fetch
works? Either way, this could use some tightening up as the current
language is quite vague. I think we should only let them affect the
navigate algorithm. Either way, we should clarify where the URL
translation happens as that will affect Service Workers (latest name
of Navigation Controller).

Received on Wednesday, 18 September 2013 12:02:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:13 UTC