W3C home > Mailing lists > Public > www-tag@w3.org > November 2012

Re: ACTION-746: Raise a bug on registerContentHandler and registerProtocolHandler to ask for specification of how fragids are handled

From: Noah Mendelsohn <nrm@arcanedomain.com>
Date: Mon, 26 Nov 2012 20:26:30 -0500
Message-ID: <50B416C6.8000605@arcanedomain.com>
To: Jeni Tennison <jeni@jenitennison.com>
CC: Larry Masinter <masinter@adobe.com>, www-tag@w3.org
Larry & Jeni: let me know if you'd like to discuss this on Thursday please. 
Thank you.

Noah

On 11/7/2012 1:49 PM, Jeni Tennison wrote:
> Larry,
>
> I took on raising this bug when you raised it as an issue during the F2F. Looking at the spec text at
>
>    http://www.w3.org/TR/html5/system-state-and-capabilities.html#custom-handlers
>
> I can't see that anything needs to change. The URL "templates" that are passed into the registerContentHandler() and registerProtocolHandler() functions don't seem to be restricted, and the URL that's constructed by replacing the %s in the template is navigated to in the same way as a URL in a @href attribute, with fragment identifiers managed in the same way.
>
> What did you think the section needs to say about fragment identifiers?
>
> Jeni
>
Received on Tuesday, 27 November 2012 01:26:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 November 2012 01:26:58 GMT