Closed Bug 7494 Opened 25 years ago Closed 24 years ago

applying font to adjacent text gives multiple font tags in HTML code

Categories

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

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: sujay, Assigned: mozeditor)

References

Details

using 6/2 build of apprunner

1) launch apprunner and editor
2) highlight some text in editor window
3) apply a different font size
4) repeat

then do Debug | Output HTML and notice that there are several font tag
containers..There should only be 1 font tag, the very last one chosen


<h2>Ender Editor Test Page</h2>
<p>This is a goo<font size="-2"><font size="-1"><font size="0"><font size="-1">d
 place to add </font></font></font></font>in html to aid in testing features
Assignee: kostello → buster
Status: NEW → ASSIGNED
Summary: apllying font multiple times gives multiple font tags in HTML code → applying font multiple times gives multiple font tags in HTML code
the code should be clever enough to detect that the <tag attribute=value> just
needs its value changed, not a whole new tag.
Severity: normal → minor
Priority: P3 → P4
Target Milestone: M11
fixed.  There is a separate problem that adjacent text nodes sometimes get
created needlessly, leading to output like this:
a<font size=+1>b</font><font size=+1>c</font>
which isn't "wrong" the way the problem originally reported in this bug is
wrong, but still should get cleaned up.  Leaving this bug open for that problem,
making it M11 low priority P4 severity minor.
Summary: applying font multiple times gives multiple font tags in HTML code → applying font to adjacent text gives multiple font tags in HTML code
changing summary to reflect bug buster describes above
Depends on: 10778
Target Milestone: M11 → M12
Target Milestone: M12 → M15
M15
This sounds like a joe thing; eliminating excess nodes.
Assignee: buster → jfrancis
Status: ASSIGNED → NEW
accepting bug
Status: NEW → ASSIGNED
P1 for M15 (focus area for Joe)
Priority: P4 → P1
fixed
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
verified in 4/6 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.