- From: James Hopkins <james@idreamincode.co.uk>
- Date: Mon, 27 Apr 2009 01:09:46 +0100
- To: Boris Zbarsky <bzbarsky@MIT.EDU>
- Cc: Aryeh Gregor <Simetrical+w3c@gmail.com>, "www-style@w3.org" <www-style@w3.org>
On 22 Apr 2009, at 01:45, Boris Zbarsky wrote: > Aryeh Gregor wrote: >> So while #foo#bar isn't really a case to get concerned about -- >> it can't mean anything useful anyway > > Actually, between xml:id and DOM3's ability to flag Attr nodes as > IDs, it can. **A bit more XML than CSS** OK, I would just like to clarify this point, so I'm clear what the situation is. I'm not too hot on my XML, but after having done some research on how ATTLIST declarations are able to map name-value pairs with elements, and xml:id, it appears that only one token is allowed for type ID. Are you saying that DOM3 (I presume you mean this feature? (http://www.w3.org/TR/DOM-Level-3-Core/core.html#Attr-isId) ), extends this so we're able to match a subset of ID tokens, like we can currently with the class attribute in HTML? If this is the case, then #valid#selector would presumably correctly match the space- separated type ID values, 'valid' and 'selector'.
Received on Monday, 27 April 2009 00:10:24 UTC