W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2012

[whatwg] Proposal: Deprecate registerProtocolHandler/registerContentHandler via Web Intents

From: James Hawkins <jhawkins@google.com>
Date: Tue, 21 Feb 2012 11:41:59 -0800
Message-ID: <CAO800SxpnPn9DZec0p+nm9rigmNMs0a9SQZSiMN7AMjDcphZOg@mail.gmail.com>
On Tue, Feb 21, 2012 at 11:31 AM, Bjartur Thorlacius
<svartman95 at gmail.com> wrote:
> ?ann ?ri 21.feb 2012 18:44, skrifa?i James Hawkins:
>
>> I'm not sure if the proposal was explicit enough, but for the RPH-esque
>> functionality in Web Intents, we activate WI in the same circumstances
>> RPH is activated, which is when links are activated in a page. ?Can you
>> elucidate how the scenarios you listed could be handled? ?Note these
>> scenarios are above and beyond RPH, but we're not trying to make the API
>> self-limiting.
>
> Windows Explorer (the file manager) does for example offer users to edit
> images upon right-click. I worry that if URI scheme handlers need not only
> take care of fetching but also of presentation, other actions than view will
> be unnecessarily hard to implement. Thus I figure retrieval and presentation
> must be separated.
>
> (view (fetch uniform:resource/locator))
> or
> (edit (fetch uniform:resource/locator))
>
> instead of
> (fetch-and-view uniform:resource/locator)

Is this use case not fully handled by the UA specifying the
appropriate action when building the intent, e.g., the user
right-clicks on an image in a page and the UA constructs context menu
items for edit/share/etc. action?
Received on Tuesday, 21 February 2012 11:41:59 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:40 UTC