Never say never

Posted on September 12, 2007 by Ilfak Guilfanov

I never thought that I’d be directly hit by an IE bug. However, it happened today. This page:
http://www.hex-rays.com/compare.shtml
does not render correctly in IE7. I tried everything, got rid of all validator complaints, rearranged the code, played with the css file, and finally checked the IE bug collections.
Okay, I give up.
Where should I submit the bug or seek help?

This entry was posted in Programming. Bookmark the permalink.

8 Responses to Never say never

  1. igorsk says:
    September 12, 2007 at 04:00

    Looks okay here. Nice examples, by the way! Does it detect all the “magic division” constants?

  2. Nicholas Sherlock says:
    September 12, 2007 at 06:06

    Seems to render just fine here, IE7, Windows XP. What exactly renders wrong on your machine?

  3. David says:
    September 12, 2007 at 07:11

    Does it render correctly in some other browser?
    In Firefox 2 on Linux it looks like you at least need some newlines in the disassembly.
    Regards,
    \David

  4. Ilfak Guilfanov says:
    September 12, 2007 at 11:47

    It renders ok in all browsers except IE7. The result seems to be pretty random. Very often the first example renders correctly but the rest are garbled. It goes really bad at the end:
    http://www.hexblog.com/ie7bug.png
    I tested this on 3 different machines with IE7 and on 6-7 machines with other browsers.

  5. Ilfak Guilfanov says:
    September 12, 2007 at 11:48

    Igor, yes it tries to detect all magic constants. I tested the first 1000 but did not go further.

  6. sylvain says:
    September 15, 2007 at 21:43

    generally if you get more simple, you avoid bugs. for example, you have span for all, even only to signal a text color.
    you should use code, and font color=green instead of two span.
    more generally again, screwing up all code, then trying to reinsert it slowly, you will find what goes wrong for ie7.
    np for me linux firefox2.

  7. HHS says:
    October 2, 2007 at 04:25

    The same problem is present in IE 6. It appears to only be present on the lines that start with the beginning of a span after the spaces. Try extending the previous span so that it ends on the new line, or use BR tags instead of 0D 0A.

  8. Ilfak Guilfanov says:
    October 8, 2007 at 19:59

    Thanks to the patient help of Yin Xie from Microsoft the issue has been solved.
    Hope I didn’t break anything in the process ;)