Borders and padding set on inline area do not contribute to the calculation of line boxes. A border set on an inline element should therefore not influence the position of a border set on a block-level element. The bug is described and shown in section (4) of the test page.

Section (6) pf the test page shows another effect of what I believe is the same bug.

Specwise, this is described in section 4.4 of CSS1: "Note that any padding, border or margin above and below non-replaced inline elements does not influence the height of the line. In other words: if the 'line-height' is too small for the chosen padding or border, it will overlap with text on other lines."

*** Bug 1606 has been marked as a duplicate of this bug. ***

Borders and padding on inline elements are now also messing up the baseline. Of course, correct implementation would fix this problem... This is also now seen in the new version of the CSS1 Test Suite: in tests 4.2, 5.5.11b, 5.5.12b, 5.5.13b, 5.5.14b, 5.5.15b, 5.5.16b, 5.5.17b, 5.5.18b, 5.5.20b, and 5.5.22b .

Margins shouldn't contribute either... that is, top and bottom margins on inline elements shouldn't do *anything*.

Related to this whole problem is the problem that lines containing underlined links have more space below them in http://style.verso.com/boxacidtest/vd/

Setting all current Open/Normal to M4.

The issues with border/padding on inline elements have been repaired. However, there are still several other issues on this page, including how borders are rendered in a situation where the inline element is continued on multiple lines. So I'm reassigning this temporarily to michaelp so that he can fix up the rendering issues and then reassign it back to me.

assigning ChrisD as QA assigned to

As Kipp noted in 2/23 comments, 'the issues with border/padding on inline elements have been repaired'. Using 5/25 Apprunner, I am verifying that these issues are fixed. Section (4) in the sample URL displays properly. Closing this bug up and opening a new bug #7126 for residual issues mentioned in 2/23 comments.