Closed
Bug 321310
Opened 20 years ago
Closed 20 years ago
Varying bottom-border size of an <li> element in <ul> when using ems for size
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 287624
People
(Reporter: codethief, Assigned: dbaron)
References
()
Details
(Keywords: testcase)
Attachments
(1 file)
|
426 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8) Gecko/20051111 Firefox/1.5
I created a website design with a navigation similar to the example page and tested it under Firefox 1.0.7 - everything was ok.
After having updated Fx to 1.5 i saw some bottom borders of li elements which were thicker than the rest. I think, there's a rhythm of thick and thin lines, which depends on the set (grand-)parent's font size and of course the border size of the li element.
Reproducible: Always
Steps to Reproduce:
1. Create a <ul>-list as usual.
2. CSS: Set the font size of <body>, <ul> and the border size (i recommend using border top or bottom) of the li elements in em
[3. Sometimes there isn't anything to see. Then "play" with the font and border sizes until you see it]
Actual Results:
There's a list with list elements which have different border sizes.
Expected Results:
All borders should be equal regarding the thickness.
Updated•20 years ago
|
Assignee: nobody → dbaron
Component: General → Style System (CSS)
OS: Windows XP → All
Product: Firefox → Core
QA Contact: general → ian
Hardware: PC → All
Summary: every x. bottom border of a li element is thicker than the others after fx 1.0 -> 1.5 update → Varying bottom-border size of an <li> element in <ul> when using ems for size
Version: unspecified → 1.8 Branch
| Assignee | ||
Comment 1•20 years ago
|
||
*** This bug has been marked as a duplicate of 287624 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Comment 2•20 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•