Closed
Bug 293772
Opened 20 years ago
Closed 11 years ago
jroller.com - <li> without ol or ul gets shifted left
Categories
(Tech Evangelism Graveyard :: English US, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: palfrey, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050510 Firefox/1.0+ Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050510 Firefox/1.0+ An <li> tag without an enclosing <li> or <ul> gets shifted leftwards. See for example http://www.jroller.com/page/fate/20050419#my_tackle_is_lighter_than. Note that the example page is marked as HTML 4.01 Transitional (and page info says it's in Standards Compliance Mode), but this makes it not actually valid. Gecko shouldn't shift the <li> items left, and in the example page they should be on the right hand side of the dashed line. Reproducible: Always Steps to Reproduce: 1. Goto http://www.jroller.com/page/fate/20050419#my_tackle_is_lighter_than 2. Look at the list starting "It's simple" Actual Results: The list is shifted to the left of the dashed line Expected Results: It should be on the right hand side
Comment 1•20 years ago
|
||
the default position for the bullets is "outside". See: http://www.w3.org/TR/REC-CSS2/generate.html#propdef-list-style-position When the <li>'s parent is <ul>, Mozilla makes its position "inherit". In quirks mode, Mozilla forces them to be inside: http://lxr.mozilla.org/seamonkey/source/layout/style/quirk.css#53 ==> Tech Evang
Assignee: nobody → english-us
Status: UNCONFIRMED → NEW
Component: Layout: Block and Inline → English US
Ever confirmed: true
Product: Core → Tech Evangelism
QA Contact: layout.block-and-inline → english-us
Summary: <li> without ol or ul gets shifted left → jroller.com - <li> without ol or ul gets shifted left
Version: Trunk → unspecified
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
Updated•10 years ago
|
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•