User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20020930 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20020930 Look at the page. The third column is shifted to the top (or the 1st and 2nd column shifted to the bottom?) I've seen the code but I can't find anything wrong, except that there is a </p> at the end of each <tr> element. I suspect it's because of <pre> which forces a newline before it. I'm wondering if it's really necessary to do so. Can't <pre> (and all kind of block elements) be more intelligent not to do so when it's already at the beginning of a new line? Reproducible: Always Steps to Reproduce:
Confirming bug with 2002100317, the problem seems to be related to the <pre> tags, or the <a name=..."> tags. As you can see in the simplified testcase, if you remove either one of them, the alignment problems disappear.
The <pre> has a margin by default. In quirks mode, we remove the margin of the first child of a table. But in this case, the first child is <a>, not <pre>, so the margin does not get removed. Our existing quirk works for enough pages that I don't see a really good reason to change it...
The site's been redesigned, and the current JSref looks OK now. Since this seems to have really been a site problem, marking FIXED.