Closed Bug 1052 Opened 26 years ago Closed 26 years ago

Top borders are a pixel too thin

Categories

(Core :: Layout, defect, P2)

x86
Other
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: dbaron, Assigned: kmcclusk)

References

()

Details

Top borders seem to be a pixel too thin. This is especially noticeable in the thin border in the above URL.‰
Status: NEW → ASSIGNED
Assignee: kipp → peterl
Status: ASSIGNED → NEW
This has been identified as a rounding issue with borders that are "thin", "medium" or "thick".
I don't think it all has to do with thin, medium, and thick. The left border in http://www.w3.org/Style/CSS/Test/current/sec412.htm is a pixel too thin on its left side (note that the pixel ruler is 2px off!). In other tests: sec5513b: The thin border on the inline element is thinner inside the table. sec5515b: The border is thinner on the bottom and the right outside the table and thinner on the right inside the table. sec5522: The thin maroon border is thinner on the bottom and the double one varies by side. However, some of this may be related to bug 591.
Setting all current Open/Normal to M4.
All the problem in the sec55* pages are now fixed, I think, except the double border in sec5522.htm
Now the top border in sec5515 (the above URL) is a px too thick, instead of too thin. Was this corrected in 2 places? (i.e, gfx code and workaround)
per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Assignee: peterl → michaelp
Target Milestone: M4 → M5
The style code has been changed so that borders are computed in pixel instead of points. Any rounding issues left are in the rendering code...
I don't see any rounding issues left...
Assignee: michaelp → kmcclusk
kevin, can you confirm this and mark it fixed if necessary?
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Looks fine. Brought up URL, examined the borders with ZoomIn.exe. Marking it as fixed.
Status: RESOLVED → VERIFIED
Verified fixed.
You need to log in before you can comment on or make changes to this bug.