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

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

From: Jeni Tennison <jeni@jenitennison.com>
Date: Wed, 7 Nov 2012 18:49:19 +0000
Message-Id: <196507BC-D1BF-4627-9C60-B9BB9FD4DE78@jenitennison.com>
Cc: www-tag@w3.org
To: Larry Masinter <masinter@adobe.com>
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
-- 
Jeni Tennison
http://www.jenitennison.com/
Received on Wednesday, 7 November 2012 18:49:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 7 November 2012 18:49:43 GMT