Web Analytics Made Easy -
StatCounter CSS Menu Help Needed - IE .htc problem - CodingForum


No announcement yet.

CSS Menu Help Needed - IE .htc problem

  • Filter
  • Time
  • Show
Clear All
new posts

  • CSS Menu Help Needed - IE .htc problem

    Hey guys,

    The problem is the fact that IE doesn't support :hover. Shame on them, but anyway. I found that this shortcoming can be emulated by using the .htc behavior file within CSS - GREAT!

    So here's my problem. The first list item uses a different background image than the other list items. Although I can get this working if I use the same background image I just can not figure out how to get the first list item to work correctly without affecting the rest of the list items.

    If you look at it in Firefox, it works perfectly. What am I doing wrong in IE? If anyone has any experience with this, please help. Thank you in advance.

    Here's the link to the test page:


  • #2
    I think your problem is related to yet another IE bug with multiple class definitions which is illustrated by the following file:
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-gb">
    <meta http-equiv="Content-type" content="text/html; charset=US-ASCII" />
    <title>IE Multiple classes test</title>
    <script type="text/javascript">
    <style type="text/css">
      { color: red;
      { font-weight: bold;
      { font-style: italic;
    <h1>Internet Explorer Multiple Class Selector Bug Demonstration</h1>
    <p class="red">This paragraph should be red.</p>
    <p class="bold">This paragraph should be bold.</p>
    <p class="red bold">This paragraph should not only be red and bold, but also italic</p>
    Notice what IE does to the first paragraph.
    Vladdy | KL
    "Working web site is not the one that looks the same on common graphical browsers running on desktop computers, but the one that adequately delivers information regardless of device accessing it"


    • #3
      Well that would make sense. Wasn't aware of that, so thank you for the info.

      Is anyone aware of a work-around for this IE bug?