- From: Chris Lilley <chris@w3.org>
- Date: Fri, 9 Mar 2012 17:37:43 +0100
- To: Robin Berjon <robin@berjon.com>
- CC: Eric A. Meyer <eric@meyerweb.com>, public-cssselfrags@w3.org
On Friday, March 9, 2012, 1:45:41 PM, Robin wrote: RB> On Mar 8, 2012, at 19:44 , Chris Lilley wrote: >> On Thursday, March 8, 2012, 4:54:58 PM, Robin wrote: >> RB> "Your application has been reviewed and was found to be >> RB> in error, please make sure that you correct these fields: >> RB> http://kafka.org/bureau/form2035.html#css(:invalid)". >> Mention of "these fields" reminds me that the specification should say explicitly that a fragment identifier may match multiple nodes and that all matched nodes (not, for example, just the first one or just the last one or whatever) are pointed to by the fragment identifier. RB> It could perhaps use some RFC2119 finessing, but I think we're covered by: RB> """ RB> If a location-set contains multiple nodes, the processor should RB> consider that this fragment identifier is pointing to all of them RB> simultaneously (e.g. for :target processing for instance). That part is good. RB> However, the identification of multiple results may not be RB> appropriate in some contexts. In these contexts, the processor RB> must return only the first result in document order. RB> """ That part is wooly and largely negates the clarity of the first part. -- Chris Lilley Technical Director, Interaction Domain W3C Graphics Activity Lead, Fonts Activity Lead Co-Chair, W3C Hypertext CG Member, CSS, WebFonts, SVG Working Groups
Received on Friday, 9 March 2012 16:40:27 UTC