Closed
Bug 503425
Opened 15 years ago
Closed 15 years ago
[qmo2] Ordered list missing number prefix
Categories
(quality.mozilla.org :: Website, defect, P2)
quality.mozilla.org
Website
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: whimboo, Assigned: paulc)
References
()
Details
When you are using ordered list in documents the numbering is not visible. I'm able to see this at least on quality.authstage.mozilla.com. Use something like this in the richtext editor: 1. First item 2. Second item
Updated•15 years ago
|
Priority: -- → P2
Assignee | ||
Comment 1•15 years ago
|
||
r29579 added a bit of CSS. https://quality.authstage.mozilla.com/blogs/paulc/test-title
Assignee: nobody → paul.craciunoiu
Target Milestone: --- → 1.0
Assignee | ||
Comment 2•15 years ago
|
||
Should test this for regressions on other QMO pages.
Comment 3•15 years ago
|
||
looks great!! yay, numbered/ordered lists ftw in authstage
Reporter | ||
Comment 4•15 years ago
|
||
Already mentioned on IRC but also check nested lists.
Assignee | ||
Comment 5•15 years ago
|
||
Created: https://quality.authstage.mozilla.com/blogs/paulc/test-nested-lists Looks good. r29746
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 6•15 years ago
|
||
Has something been broken the rich test editor? The toolbar shows both buttons pushed for ul and ol lists when clicking on "item ul nested 1".
Assignee | ||
Comment 7•15 years ago
|
||
That's probably because of nested lists, you're inside both a ul and ol. Does something not WORK (functionality-wise)?
Reporter | ||
Comment 8•15 years ago
|
||
Try to switch this row into a ul. It will not work. Also creating a new sub ordered list for this item I cannot get to work. Just wanted to add a ol/ul/ol to check if this path also works because it is missing.
Assignee | ||
Comment 9•15 years ago
|
||
(In reply to comment #8) > Try to switch this row into a ul. It will not work. Also creating a new sub > ordered list for this item I cannot get to work. Just wanted to add a ol/ul/ol > to check if this path also works because it is missing. That's not related to this bug. This is just how tinymce handles nested lists. I'm sure you can find lots of glitches :) I made it work by selecting both 'item ul nested 1' and 'item ul nested 2' and unselecting "ul" button, then de-selecting and selecting ol. ... Such are the quirks of tinymce (our richtext editor).
Reporter | ||
Comment 10•15 years ago
|
||
That's true. Ok, so I have updated your test page and noticed that the left indentation is not correct for ordered lists when comparing them to unordered lists. That applies to all levels in the hierarchy.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 11•15 years ago
|
||
Not correct? Can you be more specific?
Assignee | ||
Comment 12•15 years ago
|
||
Please file a new bug if you want to change the padding. In CSS, however, they use the same padding (20px). I think this is a minor issue and it's not very noticeable (or perhaps I'm missing something). At any rate, it's not about missing the number prefix and therefore out of the scope of this bug. It's better to keep to few commits per bug, to keep track of things easily.
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 13•15 years ago
|
||
Paul, this is more then obvious to see. Please check your example page. Ordered sub lists show the numbering at the parents level. Which is not a minor issue IMO and can definitely be fixed in this bug because your patch r29746 doesn't take the outside value of the ul property into account. And as far as I can see it hasn't been pushed live yet.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 14•15 years ago
|
||
I don't get it...
Reporter | ||
Comment 15•15 years ago
|
||
I have updated your test page. Check the Test alignment section.
Comment 16•15 years ago
|
||
Henrik, I don't want to block the push of bugs for the QMO 1.0 milestone because of this minor issue. Please open a new bug and it'll be taken care of in the next one. I'm moving this to resolved:fixed.
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → FIXED
Updated•14 years ago
|
Target Milestone: 2.0 → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•