On Thu, Jun 9, 2011 at 11:03 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 6/9/11 10:56 AM, Tab Atkins Jr. wrote: >> >> It definitely wouldn't be a parse error. It would produce a selector >> equivalent to "::after::before", which is just an invalid selector. > > That selector is a parse error, last I checked. > > Or are we using different definitions of "parse error"? Yes. I think my definition is inconsistent, so let's just call it a parse error. ~TJReceived on Thursday, 9 June 2011 18:12:42 GMT
This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:41 GMT