3366 - adjacent sibling selector quirks

Status: VERIFIED FIXED

(Core :: CSS Parsing and Computation, defect, P2)

Description

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Here are two problems with adjacent sibling selectors (1999-03-02 Win95 opt
build):

1) We seem to interpret the spec's statement "immediately precedes"
differently.  I think anonymous elements between should count as something
between.  That's not what you're doing.  See the test with a "(??)" in the
above URL, where you are applying (I think incorrectly) the EM + STRONG
selector.

2) They don't work with class selectors.  This is nasty to parse, but
.warn+.rant ought to work.  Again, see above URL.  (Child selectors are fine
for this test.  See childsel.html in the same directory.)

Comment 1

[Peter Linss]

#1 is behaving correctly according to current consensus in the CSS w/g. This
issue has been discussed and may change. We'll comply with the w/g position.

#2 is a bug in the CSS tokenizer. Fix will be checked in later today. (was
taking '+.rant' as the number '+.' in 'rant' units, now it confirms that a digit
follows the '.' before presuming a number after '+.' or '-.')

Comment 2

[Peter Linss]

Checked in.

Comment 3

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Verified fixed.

I can see the WG position on #1 because of whitespace issues.