Open Bug 122883 Opened 23 years ago Updated 2 years ago

Margins not always displayed around uls and ols

Categories

(Core :: DOM: Editor, defect, P3)

defect

Tracking

()

mozilla1.5beta

People

(Reporter: slogan, Unassigned)

Details

(Whiteboard: EDITORBASE+)

Steps:

Open a new composer window
click on the ul button
type in 4 lines, you should get a ul with 4 li children
click at the end of the second item in the list
hit return, you will get a li with nothing in it
hit shift-tab to get rid of the bullet

Results: 

You'll get a blank line between the two lists, a blinking caret at position 0 of
that line, and no vertical spacing between that line and the lists above and
below. If you save the document and reopen it, you will see the blank line, and
there will be vertical space above and below the blank line due to margins or
padding added around lists.

Expect Results:

Same as the observed results, except there is padding/margin between the blank
line and the lists above and below.  

Why is this a bug? Well, if you create two lists, they will have padding between
them that looks exactly as though there is a blank line. But the user will not
be able to click in there, and it will appear to be a bug when in fact it is
not. If we show the margins like we should be, always, then when there is a
blank line between the lists, the vertical space will be much taller; the user
will be able to visually tell the difference (with a bit of experience) between
two lists with no blank line between them, and two lists with one or more blank
lines. Until I learned we put margins around lists, I was continually frustrated
by not being able to click in what appeared to be a blank line. Now that I know
this, I get equally frustrated when I can't tell if that white space is due to
margins, or it is a blank line and the margins were not drawn because layout did
not reflow.

See related bug 114991
Keywords: nsbeta1+
Whiteboard: EDITORBASE+
Target Milestone: --- → mozilla1.0
Oops, related bug is 114911 (sorry about the typo)
Nothing we can really do about this.
Keywords: nsbeta1+nsbeta1-
Whiteboard: EDITORBASE+ → EDITORBASE-
Target Milestone: mozilla1.0 → mozilla1.2alpha
This is just layout behavior, right?
Severity: critical → normal
Target Milestone: mozilla1.2alpha → mozilla1.2beta
Priority: -- → P3
Target Milestone: mozilla1.2beta → mozilla1.3beta
EDITORBASE+
QA Contact: sujay → beppe
Whiteboard: EDITORBASE- → EDITORBASE+
>hit shift-tab to get rid of the bullet

This doesn't have any effect for me. Has some behaviour changed in the editor
since this bug was reported?
Target Milestone: mozilla1.3beta → mozilla1.5alpha
Target Milestone: mozilla1.5alpha → mozilla1.5beta
QA Contact: rubydoo123 → editor
Assignee: kinmoz → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.