Closed Bug 99765 Opened 23 years ago Closed 22 years ago

Indent Twice the content will move a little bit on screen

Categories

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

x86
Windows NT
defect

Tracking

()

RESOLVED DUPLICATE of bug 61949
Future

People

(Reporter: wkfx2003-bugzilla, Assigned: kinmoz)

References

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4+)
Gecko/20010914
BuildID:    2001091403

.

Reproducible: Always
Steps to Reproduce:
1. New Message
2. Type "a" in the body, leave the cursor after "A"
3. Press "Indent Text" button on format toolbar twice

Actual Results:  "A" moved down a little bit

Expected Results:  "A" remains in the same horizontal level
over to editor
Assignee: ducarroz → kin
Component: Composition → Editor: Core
Keywords: mailtrack
Product: MailNews → Browser
QA Contact: sheelar → sujay
This is a dup of bug 61271 that was marked INVALID.

dbaron, should the top margins of nested blockquotes at the very top of the
document be applied? I noticed that if you have one blockquote at the top of the
doc, the top-margin isn't applied. But if you nest one underneath it, you get
the top-margin, and if you nest more underneath that one, you still only get the
the top-margin that was applied after the 2nd blockquote.
Status: UNCONFIRMED → NEW
Ever confirmed: true
You don't see the margin after the first indent because of a rule in quirk.css
(look for selectors body > blockquote:first-child and td >
blockquote:first-child).  We could remove blockquote from that rule to solve the
problem.  Those rules are a not-quite-complete attempt to emulate 4.x's quirk of
not displaying outer margins on body and TD.  Nobody has yet thought of a better
way to emulate this quirk without causing significantly worse problems (i.e.,
ignoring author-specified rather than UA-specified margins).

The reason adding a third indent doesn't add anything is that all adjacent
vertical margins collapse.
Well, an easy way.  We could start adding values to margin all over the place,
but that's hard...
Depends on: 33784
--> 0.9.7
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → mozilla0.9.7
Target Milestone: mozilla0.9.7 → mozilla0.9.8
Target Milestone: mozilla0.9.8 → mozilla1.0.1
I'm pretty sure this is a dup of bug 61949.
(But how can that be, if this has already been assigned,
and that one is still NEW ?)
Target Milestone: mozilla1.0.1 → Future

*** This bug has been marked as a duplicate of 61949 ***
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.