Closed
Bug 307171
Opened 19 years ago
Closed 19 years ago
Bullet images are rendered with wrong size when using whitespace and block elements inside list item
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: bugzilla, Unassigned)
References
()
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 When a <li> element contains whitespace followed by a block element, the bullet image is clipped and offset as if it were rendered in the space that would be occupied by the default list bullet disc. Reproducible: Always Steps to Reproduce: See URL Actual Results: The upper left 6x6 pixels of the bullet image are rendered in place of the bullet. After a refresh, the bullet is not rendered at all. Changing the text size fixes the display until the next refresh. Expected Results: The whole bullet image should be rendered. The whitespace might or might not be stripped, however, this should not affect bullet display. The workaround is to explicitly remove the whitespace from the page source.
Might be related to bug 279122 "incorrect rendering of unordered list item - bullet images".
Comment 4•19 years ago
|
||
I dont see this problem, please try on a more recent nightly build of firefox. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050905 Firefox/1.6a1 ID:2005090507
On Mozilla Firefox 1.5 Beta 1, the problem is not reproduced. My apologies for not trying this before reporting. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Updated•19 years ago
|
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Comment 6•19 years ago
|
||
No known bug to dupe to and not fixed by a patch -> WFM
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•