Closed Bug 156202 Opened 23 years ago Closed 23 years ago

no way to get bold numbers/letters in an <OL>

Categories

(Core :: Layout, defect)

x86
Linux
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 38174

People

(Reporter: jwz, Assigned: attinasi)

Details

In NS4, you could do <B><LI></B> to get the 1/2/3/A/B/C to be bold. That no longer works in Mozilla: now you get free line breaks. For example: <P><OL> <B><LI> This heading has a bold "1."</B> <P> ...which is as expected. <P> <B><LI></B> This heading has a linebreak after the "2." <P> ...which is not what I want. I want the "2." to be bold, and the text after it on the line to be non-bold. <P> <B><LI> This</B> heading has a linebreak after the "This." <P> ...which is clearly not what I wanted. <P> </OL>
The markup in question is invalid... And the rest is a duplicate of "[LIST] List numbers and bullets ignore FONT changes" *** This bug has been marked as a duplicate of 38174 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Verified.
Status: RESOLVED → VERIFIED
I don't care whether the markup is invalid, it used to work in every previous version of the browser. How do I get the effect of a bold number and non-bold text on the same line? I don't see a way to do it without the markup I used.
However, Mozilla _does_ care if the markup is invalid. What you're looking to do can (theoretically) be achieved using CSS2 Markers: http://www.w3.org/TR/REC-CSS2/generate.html#q11 Example ------- <style type="text/css"> li:before { display: marker; content: counter(counter) " "; counter-increment: counter; font-weight: bold; width: 6em; text-align: center; } </style> <ol> <li>This is the first item.</li> <li>This is the second item.</li> <li>This is the third item.</li> </ol> ...but Mozilla doesn't support CSS2 counters yet (see ye olde bug 3247), so it really comes down to how badly you want to see bold markers.
So what you're saying is: - we won't support the old way of accomplishing what you want, for ridiculous ideological reasons; - we don't support the new, less portable way of accomplishing what you want, because it's too hard; - so your pages look wrong, and we are redefining that to be "right".
You need to log in before you can comment on or make changes to this bug.