W3C home > Mailing lists > Public > public-media-fragment@w3.org > May 2012

Re: How URL Fragments could interact with Selectors, MQ and CSS, incl. Variables

From: Christoph Päper <christoph.paeper@crissov.de>
Date: Tue, 29 May 2012 15:54:06 +0200
Cc: public-media-fragment@w3.org
Message-Id: <B13B9FDB-EA59-4058-B526-CEEE41AB8412@crissov.de>
To: www-style list <www-style@w3.org>
Julian Reschke:

> note that HTML5 (via DOMCORE) closed the door on extending the identifier format, because it makes pretty much everything a legal id.

Do you mean this bit? <http://www.w3.org/TR/domcore/#concept-id>:

>> An element has an ID if it has an id attribute whose value is not the empty string.
>> The ID is that attribute's value.


That doesn’t seem to say anything about the use of IDs in fragment identifiers, where they could be percent-escaped as necessary. That means

  <a id="foo=bar">

should be referenced by

  #foo%3Dbar

and not by

  #foo=bar

The “scroll to the fragment identifier” algorithm currently described in HTML5 could (and probably should) be extended in step 7 to support other methods than simple IDs, names and keywords. <http://www.w3.org/TR/html5/Overview#scroll-to-the-fragment-identifier> 

Note that there is a reference to RFC 3023 for HTML documents with an XML MIME type. This in turn mentions (a WD of) XPointer.
<http://tools.ietf.org/html/rfc3023#page-15>
Received on Tuesday, 29 May 2012 13:54:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 29 May 2012 13:54:52 GMT