Closed
Bug 95453
Opened 25 years ago
Closed 23 years ago
highlighting text and clicking on 'Left Align' adds <br>
Categories
(Core :: DOM: Editor, defect, P3)
Core
DOM: Editor
Tracking
()
VERIFIED
FIXED
mozilla1.4beta
People
(Reporter: shrir, Assigned: mozeditor)
Details
(Whiteboard: EDITORBASE-; 2 day?; [rules])
Attachments
(1 file)
|
297 bytes,
text/html
|
Details |
win 0815 trunk
steps:
1 launch composer and open the file attached
2 highlight the 'second line' and click on 'Left Align' in toolbar
3 Observe that the 'second line' gets pushed to the third line and caret goes to
far left on second line
expected: Contents of the second line should go to the left and should not get
pushed down
| Reporter | ||
Comment 1•25 years ago
|
||
Comment 2•25 years ago
|
||
actually what is happening is that an extra div is being inserted with a br.
When the second line is aligned left, the two lines are incorrectly broken
apart. To reproduce this problem -- do the following steps:
1. enter both lines of text on the same line
2. highlight the entire line and set the formatting - b,i and u
3. while the line is still selected, align center
4. set the caret to where you want to break the line, and hit enter
look at the code - you will see this:
<div align="Center"><u><i><b>line one<br>
line two</b></i></u></div>
5. set the caret in the second line and select align left, the code now looks
like this:
<div align="Center"><u><i><b>line one<br></b></i></u>
<div align="Left"><br></div>
<u><i><b>line two</b></i></u>
</div>
The resulting code should be this:
<div align="Center"><u><i><b>line one</b></i></u></div>
<div align="Left"><u><i><b>line two</b></i></u></div>
the result will be as expected, teh second line will be left aligned and there
will not be a blank line in between
Assignee: beppe → jfrancis
Priority: -- → P3
Whiteboard: [rules]
Target Milestone: --- → mozilla1.0
| Assignee | ||
Comment 3•25 years ago
|
||
097
Status: NEW → ASSIGNED
Target Milestone: mozilla1.0 → mozilla0.9.7
| Assignee | ||
Updated•24 years ago
|
Whiteboard: [rules] → EDITORBASE; 2 day?; [rules]
| Assignee | ||
Updated•24 years ago
|
Target Milestone: mozilla0.9.7 → mozilla0.9.8
Comment 4•24 years ago
|
||
confirmed on mac os x build 2001121805, Platform/OS needs to be changed to ALL.
Comment 5•24 years ago
|
||
Changed Platform and OS to all/all per above comments.
OS: Windows NT → All
Hardware: PC → All
| Assignee | ||
Comment 6•24 years ago
|
||
pushing off 098 to 099
Target Milestone: mozilla0.9.8 → mozilla0.9.9
minusing, please beg to differ if you beg to differ
Whiteboard: EDITORBASE; 2 day?; [rules] → EDITORBASE-; 2 day?; [rules]
| Assignee | ||
Comment 8•24 years ago
|
||
the swami says: things that will not land in 099!
Target Milestone: mozilla0.9.9 → mozilla1.0
Comment 9•24 years ago
|
||
Moving bugs to Mozilla1.1 that are not EDITORBASE+.
Target Milestone: mozilla1.0 → mozilla1.1
| Assignee | ||
Comment 10•24 years ago
|
||
ugh. in recent builds hitting undo at the end of this causes text in the first
line to be replicated in the second line.
Comment 11•24 years ago
|
||
removing myself from the cc list
| Assignee | ||
Comment 12•24 years ago
|
||
The trunk is the wave of the future!
Target Milestone: mozilla1.1alpha → mozilla1.1beta
| Assignee | ||
Comment 13•24 years ago
|
||
The days of having a half dozen milestones out in front of us to divide bugs
between seem to be gone, though I dont know why. Lumping everything together as
far out as I can. I'll pull back things that I am working on as I go.
Target Milestone: mozilla1.1beta → mozilla1.2beta
| Assignee | ||
Comment 14•24 years ago
|
||
[ushing these out as far as bugzilla will let me. I'll pull them back as I work
on them.
Target Milestone: mozilla1.2beta → mozilla1.4beta
Comment 16•23 years ago
|
||
using current trunk build, this works fine now
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•