W3C home > Mailing lists > Public > www-style@w3.org > July 2011

RE: [CSS OM] list of issues

From: Sylvain Galineau <sylvaing@microsoft.com>
Date: Wed, 6 Jul 2011 22:13:23 +0000
To: Tab Atkins Jr. <jackalmage@gmail.com>
CC: Daniel Glazman <daniel.glazman@disruptive-innovations.com>, "Anne van Kesteren" <annevk@opera.com>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <3C4041FF83E1E04A986B6DC50F0178290C2B13@TK5EX14MBXC297.redmond.corp.microsoft.com>


[Tab Atkins:] 
> On Wed, Jul 6, 2011 at 1:55 PM, Sylvain Galineau <sylvaing@microsoft.com>
> wrote:
> > [Tab Atkins:]
> >> On Wed, Jul 6, 2011 at 5:08 AM, Daniel Glazman
> >> <daniel.glazman@disruptive- innovations.com> wrote:
> >> > Le 06/07/11 10:09, Anne van Kesteren a écrit :
> >> >
> >> >> Well per the current specification it would only be ":after",
> >> >> "::after", ":before" and "::before". If we allow new post CSS 2.1
> >> >> pseudo-elements it would only be "::foo" where foo is the name of
> >> >> the
> >> new pseudo-element.
> >> >
> >> > First line and first letter ? Marker ?
> >>
> >> Exactly the same answer.  :first-line and :first-letter are
> >> explicitly allowed by Selectors for legacy reasons, so they're
> >> accepted alongside the double-colon form.  ::marker has no such
> >> concern, so only the double-colon form is accepted.
> >>
> > If that the expectation then it should be explicitly stated. Fwiw,
> > WebKit does not meet your expectation today (it allows the name with no
> prefix column).
> 
> I agree it should be stated explicitly, if it's not already.  Our behavior
> is  stupid.
> 
I don't think it's stupid. It's not so obvious to me why a getComputedStyle()
argument needs this bit of selector syntax. If the argument represents the
name of a pseudo-element, there is no need for colons to disambiguate it.
Received on Wednesday, 6 July 2011 22:13:52 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:42 GMT