W3C home > Mailing lists > Public > www-style@w3.org > August 2005

Re: [CSS21] Multiple IDs

From: Malcolm Rowe <malcolm-www-style@farside.org.uk>
Date: Thu, 25 Aug 2005 16:55:04 +0100
To: Chris Lilley <chris@w3.org>
Cc: www-style@w3.org
Message-ID: <20050825155504.GC3755@lorenz.farside.org.uk>

On Thu, Aug 25, 2005 at 03:41:51PM +0200, Chris Lilley wrote:
> Removal of the wording on multiple ID attributes limits the suitability
> of CSS 2.1 to SVG and CDF. SVG and CDF WGs request that this
> functionality remain in the draft and be tested for in the test suite.

Firstly, the suggestion is to downgrade this note from normative to
informative, in order to permit CSS2.1 to exit CR, not to remove the feature

> In SVG 1.2, IDs could arise from any of these methods. Why should
> CSS selectors give different results to getElementById? Why does CSS 2.1
> propose to tolerate this variability and inconsistency, whereby
> compliant implementations can fail on a simple #foo selector?

Secondly, I don't believe that anyone is suggestion that UAs that support
multiple IDs in other ways (via getElementById, for example) should _not_
support multiple IDs via the CSS ID selector, it's just that those UAs
that don't support it in CSS don't support it anywhere else either.

But most importantly, shouldn't your comment really be directed at CSS
implementors rather than the CSSWG? It makes no sense to request the
working group leave the feature in if there are no interoperable
implementations, as CSS 2.1 won't exit CR until that happens.

[Alternatively, if you're already aware of two interoperable implementations
of this functionality, you don't need to do anything, as the feature will
only be dropped if two implementations cannot be demonstrated at the end
of the CR stage.]

Received on Thursday, 25 August 2005 15:55:14 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:20 UTC