IE 7 is released and some css handling changed.

Quote:

Cascading Style Sheet Compatibility in Internet Explorer 7
for fullstory, checkout this url.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/IETechCol/cols/dnexpie/ie7_css_compat.asp

CSS Filters

Even though standards like CSS are available it is not a guarantee that all browsers render the same way. The standard might have undefined parts, not all components are equally implemented by all browser vendors, and existing implementations might have bugs. The CSS standard does not provide a way to target specific browser versions and as a result the Web developer community has developed CSS filters (also called "CSS hacks"). These filters take advantage of browser bugs or unimplemented features to hide CSS style rules from specific browsers. As we fix these bugs and improve CSS support, some CSS filters will stop working.

If you use such filters, you should understand their effects. In this long run, this will help you create designs that more effectively adapt to improved CSS support in later versions of Internet Explorer and other browsers.

In IE7, we fixed many underlying parser bugs that prevented the following filters from working in earlier versions of IE. If your page contains these filters, please remove or replace them (at the end of this article we will offer other means of targeting reliable IE versions).

* HTML Filter

This CSS filter is based on a parser bug. It used to show rules exclusive to Internet Explorer. These constructs will now be ignored by Internet Explorer 7 and later.

Code:

/* The following rules used to apply only to
IE but now get ignored by IE7 and higher */
* html{
}

* html body{
}

* html .foo{
}

_ Underscore Filter

This CSS filter is based on a parser bug. It used to show properties exclusive to Internet Explorer. These constructs will now be treated as a "custom property" by Internet Explorer 7 and later. Custom property means that it is still in the OM and can be queried through script but does not natively apply its value.

Code:

/* The following rule used to apply min-height
to browser who understand this property and
height to IE. In IE7, _height will be treated
as a custom property (no height will be applied) */

.myclass {
min-height: 300px;
_height: 300px;
...
}

/**/ comment filter

This CSS filter is based on a parser bug. It used to hide properties exclusive to Internet Explorer under the strict doctype (this filter did not work under quirks mode). In Internet Explorer 7, the property will now be parsed and applied.

Code:

/* The following rule used to hide the height
property to Internet Explorer. In IE7, the
value will be applied */

.myclass {
height/**/: 300px;
...
}

"html > body" child selector filter

This CSS filter is based on a previously unimplemented feature in Internet Explorer. It used to hide declarations exclusive to Internet Explorer. Starting with version 7, Internet Explorer will apply the properties within the declaration.

Note: CSS style rules that rely on child selectors are only considered CSS filters when used to detect specific browsers or browser versions.

Code:

/* The following rule used to hide the height
property to Internet Explorer. In IE7, the
value will be applied */

html > body {
height: 300px;
...
}

"head + body" adjacent selector filter

This CSS filter is based on a previous non-implemented feature in Internet Explorer. It used to hide declarations exclusive to Internet Explorer. Now Internet Explorer will apply the properties within the declaration.

Note: CSS style rules that rely on adjacent selectors are only considered CSS filter when used to detect specific browsers or versions.

Code:

/* The following rule used to hide the height
property from Internet Explorer. In IE7,
the value will be applied */

Head + body {
height: 300px;
...
}

"head:first-child + body" first child and adjacent selector filter

This CSS filter is based on two previous non-implemented features in Internet Explorer (:first-child pseudo class and the adjacent selector). It used to hide declarations exclusive to Internet Explorer. Now Internet Explorer will apply the properties within the declaration.

Note: CSS style rules that combine :first-child selectors with adjacent selectors are only considered CSS filters when used to detect specific browsers or browser versions.

Code:

/* The following rule used to hide the height
property from Internet Explorer. In IE7,
the value will be applied */

head:first-child + body {
height: 300px;
...
}

S3nd K3ys

Have a look at this, this and this, then go back and re-write your post. Mkthks. Wink

'K3ys teh backseat moderator

Animal

S3nd K3ys wrote:

Have a look at this, this and this, then go back and re-write your post. Mkthks. Wink

'K3ys teh backseat moderator

Yup.

-close-