This old bug is still around in Beta 2. (along with absolute positioning bugs on the left nav...) (hmmm - seems fixed in the final release but maybe I'm just not seeing what the problem is supposed to be?)

I posted a test case and workaround on this. The trick is to set widths to the elements displayed as blocks.[11]

The bug seems fixed in RC1.

The @import rule

@import stylesheet driven sites have no a:hover. This bug is in the beta2 preview, but has already been fixed by Microsoft: "people reported that :hover would not work from an @import. That's a bug and already fixed in our builds." --Markus [MSFT] ([13]). Can be resolved in the beta by embedding #fubar a:hover {float: inherit;} in the head of the affected documents [14].

Fuzzy Specificity Bug

The fuzzy specificity bug that affects IE and Opera 7.54 and under, documented here [15], is still present in IE7 final release.

CSS Properties

background

the origin of the background, background-position: 0 0; refers to the padding edge or on the border edge, depending on the Has Layout status of the element [16]

background images get lost on multi line inline links (old problem) [17]

border

CSS 'transparent' border color still not supported; border colors set to 'transparent' are rendered instead as the font color (default is black) in IE7 [18] *** fixed in the beta release of 24 April 2006, version 7.0.5346.5 ***

display

It has been stated that the 'table*' values of the 'display' declaration will *not* be supported. (old problem) [19]

float

Elements with assigned height correctly allow floats to stick out of them, but the protruding part is ignored by the following boxes (new Jan31, Mar20) [20]

Negative top value on position:relative is deducted from border-width of relative positioned ancestor [30]

Fixed in Jun29:

position: fixed and absolute fail to shrink-wrap if a child Has Layout , i.e. ul has position: fixed and li has max-width (Mar20) [31]. But when a shrink-wrapping container (because of position: absolute/fixed, or float: left/right) has more children, the ones with hasLayout seem to separately shrink-wrap their content, which is wrong (new) [32]

Fixed in Mar20:

horizontal scrollbar due to position: relative on non-layout element (new in IE7b2) [33]

note 1: Almost every test passes; the only exception is the one that tests two attribute selectors being applied at the same time.
note 2: The only part that fails is: active, which IE7 doesn't support.
note 3: Passes :hover; fails :focus and :active. And did anyone notice that IE styles :focus as if it were :active?
note 4: Fails the list item first line test; passes everything else.
note 5: The button[value] selector doesn't work. When value is given a value (e.g. button[value="edit"]) it can make IE7 to close the window without warning

IE7 Compatibility List Support Test

Kelly found:

According to my tests on the selectors, IE7b2 supports:

> (Child)

+ (Direct Adjacent Sibling)

~ (Indirect Adjacent Sibling)

[attr] (Basic Attribute)

[attr="value"] (Attribute/Value [sort of])

[attr~="value"] (Attribute/Spaced Values)

[attr|="value"] (Attribute/Hyphen-Sep Values)

[attr*="value"] (Attribute Substring Selector)

[attr^="value"] (Attribute Starting String Selector)

[attr$="value"] (Attribute Ending String Selector)

:hover

:first-child

It doesn't support:

:focus

:active

:lang

Any CSS3 selector other than mentioned above.

Note that when I say "supports" and "doesn't support", I mean when compared to IE6. So what is supported in IE6 should be supported here (I haven't tested things like :first-line and :first-letter, though).

Also, form elements seem to show strange bugs with the selectors. Need more research on this.

(Kelly: I used Dean Edwards IE7 compatibility list to test these selectors. Obviously, the Javascript library was off.)