Closed
Bug 3385
Opened 26 years ago
Closed 26 years ago
The type attribute of <OL> and <LI> is not showing correctly
Categories
(Core :: Layout, defect, P2)
Tracking
()
VERIFIED
FIXED
People
(Reporter: jcarpenter0524, Assigned: buster)
References
()
Details
3-2-99 build Win32 (NT and Win98) (Code for the above URL is listed below) - Set the type element in an <OL> or in <LI> - the list items are not numbered (or lettered) correctly Seems to have only been broken in small ways until the build of 2\26. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD><TITLE>junk</TITLE></HEAD><BODY> One:<OL> <LI type=A>Should be an A <LI>Should be a 2 <LI type=A>Should be a C </OL> Two:<OL> <LI>Should be a 1 <LI>Should be a 2 </OL> Three:<OL type=A> <LI>Should be an A <LI>Should be a B </OL> Four:<OL start=5> <LI type=i>Should be a v <LI type=a>Should be an f </OL> Five:<OL type=a> <LI>Should be an a <LI>Should be a b </OL> Six:<OL start=5> <LI type=i>Should be a v <LI type=1>Should be a 6 </OL> Seven:<OL type=1> <LI>Should be a 1 <LI>Should be a 2 </OL> </BODY></HTML>
Sounds like the problem you mentioned this afternoon
Assignee: troy → kipp
Comment 2•26 years ago
|
||
I just started looking at the bft's and noticed that in ordered lists, even without the type attribute, the numbering is not functional. In the files that I have looked at, all OL list items are 0.
Fixed (there is a pending checkin for #3597 that will fix the lowercase counter issues for type=i and type=a so don't reopen the bug just because those come out in uppercase). The counters count properly; bug #3597 is fixed in my tree. All is now well. You got lucky and caught the codebase when the counters were broken for *1* day...sigh.
Updated•26 years ago
|
Status: RESOLVED → REOPENED
Updated•26 years ago
|
Resolution: FIXED → ---
Comment 4•26 years ago
|
||
lower roman does not render correctly, take a look at this test case: http://slip/projects/marvin/html/list_ol_li_type.html
Status: ASSIGNED → RESOLVED
Closed: 26 years ago → 26 years ago
Resolution: --- → FIXED
Please read my response last time more carefully. In it I said "there is a pending checkin for #3597 that will fix the lowercase counter issues for type=i and type=a so don't reopen the bug just because those come out in uppercase" If you had read that, you wouldn't have re-opened the bug. Bug #3597 covers this issue so we don't need two bugs for the same issue.
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Comment 6•26 years ago
|
||
I apologize Mr. Kipp, shame on me.
You need to log in
before you can comment on or make changes to this bug.
Description
•