106480 - indentation in HTML mode adds a vertical top margin

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[TucsonTester1]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.9.4) Gecko/20011022
Netscape6/6.2
BuildID:    Gecko/20011022

I made a new page in composer with 1 image(resized custom 75 pixels for width
height set to 39 and hit ok,then I put the caret in front of the image and hit
the space bar 3 times then I hit the indent button 14 times and the caret jumped
to the line above the image and they both kept moving then if you hit the
outdent back 1 to 2 hits the caret drops down where it should be

Reproducible: Always
Steps to Reproduce:
1.open new composer window
2.click on image button insert imae from
"http://www.mozilla.org/quality/browser/front-end/testcases/composer/imgmap.png"
change to custom size width 75 pixels and height 39 now hit ok 3 times
3.now place the caret infront of the image on the screen and hit the spacebar 3
times,now hit the indent button 14 times(notice how the caret jumps up top) 
4. hit the outdent now and you see that the caret coes back if you hit the
button 1 to 2 times

Actual Results:  the caret jumped to the line above the image 

Expected Results:  It should just keep indenting as long as you want

IMac
8.6 os
160 mb ram
Gecko/20011022

Comment 1

[Greg K.]

Reporter, please provide a complete ten-digit Build ID.

Testing using Mac/2001102408.

After putting one space before the image, hitting indent twice causes the image to 
descend approx. 10 pixels vertically. This can always be reproduced, and is a definite bug, 
though it isn't what's being reported here.

The other matter is different. After a certain number of additional indents (which 
depends on how wide your Composer window is), the image descends approx. 1 line, and 
the I-beam cursor move to a position on top of the image. This happens when the 
BLOCKQUOTEs are so nested that the innermost content area is now very narrow in the 
middle of the screen. (Remember that BLOCKQUOTEs are indented from both left and 
right sides by the default style.)

So, this second matter is not, in fact, a bug, because Composer MUST wrap the contents 
of the innermost BLOCKQUOTE since there isn't enough room for it to exist side-by-side. 
Composer is doing exactly what it should do.

What should probably be done about this is use CSS style to indent, rather than 
BLOCKQUOTE. Using BLOCKQUOTE for indentation is deprecated for HTML 4, which 
Composer claims to produce.

Rather than marking this INVALID, I'll change the Summary to reflect this new idea and 
confirm.

Also setting Platform/OS=All/All and Severity=Minor.

Comment 2

[Daniel Glazman (:glazou) (not active in Mozilla any more)]

Absolutely. And such an indentation mechanism is fully convered by the CSSization
of Composer in bug 77705. Marking the current bug as dup.

*** This bug has been marked as a duplicate of 77705 ***

Comment 3

[sujay]

verified.

Comment 4

[Greg K.]

Reporter, please refile another bug addressing your first issue; that is,

"After putting one space before the image, hitting indent twice causes the image
to descend approx. 10 pixels vertically. This can always be reproduced, and is a
definite bug, though it isn't what's being reported here."

Comment 5

[Boris Zbarsky [:bzbarsky]]

*** Bug 113136 has been marked as a duplicate of this bug. ***

Comment 6

[Boris Zbarsky [:bzbarsky]]

*** Bug 153121 has been marked as a duplicate of this bug. ***

Comment 7

[Boris Zbarsky [:bzbarsky]]

Bug 77705 is fixed.  This is not. Reopening

Comment 8

[Kathleen :Brade]

reassign to new placeholder

Comment 9

[Daniel Glazman (:glazou) (not active in Mozilla any more)]

changing subject according to the what is really reported here.
please note that this does not happen in CSS mode of Composer since we just
apply and increase a left margin on an enclosing div element.

Comment 10

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 11

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 12

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420