Closed Bug 76752 Opened 24 years ago Closed 23 years ago

can't change alignment after changing text to blockquote

Categories

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

defect

Tracking

()

RESOLVED FIXED
mozilla1.4beta

People

(Reporter: sujay, Assigned: mozeditor)

References

Details

(Whiteboard: [html])

using 4/19 build of netscape 1) launch netscape 2) launch composer 3) insert text 4) center align the text 5) from paragraph style menu, pull-down to blockquote 6) now click on left align button to left align the text. it doesn't work. also notice the style says Body text after attempting this.
0.9.1
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → mozilla0.9.1
Target Milestone: mozilla0.9.1 → mozilla0.9.2
just entered the text: fdsfds select center: <div align="Center">fdsfds</div> select blockquote: <blockquote> <div align="Center">fdsfds</div> </blockquote> select left align: <div align="Left"> <blockquote> <div align="Center">fdsfds</div> </blockquote> </div> shouldn't we be checking from the text node out for a DIV element? don't we have access to the fully qualified path, so we can pick off from that? and then alter that DIV element to reflect the new choice? so the code would have been this: <blockquote> <div align="Left">fdsfds</div> </blockquote>
Keywords: correctness
Whiteboard: [html]
Target Milestone: mozilla0.9.2 → mozilla1.0
There are so many problems with using divs for allignment... People are starting to push for aim/mail/composer differentiation in editor rules: I propose we use css for alignment within the composer-only rules. Then only mail will have to deal with the brokenness of divs for alignment.
I totaly agree with you Joe, Composer should be as standards compliant as it can be and start using CSS for most, if not all, format issues
Daniel, is this fixed by your patch?
Joe: I just checked; no it is not. I'll take over this bug after 102135 check-in because the case is a little bit complex.
*** Bug 98428 has been marked as a duplicate of this bug. ***
*** Bug 96467 has been marked as a duplicate of this bug. ***
Blocks: 108237
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 (you can query for this string to delete spam or retrieve the list of bugs I've moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
removing myself from the cc list
The trunk is the wave of the future!
Target Milestone: mozilla1.0.1 → mozilla1.1beta
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
migrating milestones now that there are more available. i'll pull these back as I work on them
Target Milestone: mozilla1.2beta → mozilla1.4beta
fixed by earlier work by glazman
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.