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

VERIFIED FIXED in M15

Status

()

Core
Editor
P1
minor
VERIFIED FIXED
19 years ago
17 years ago

People

(Reporter: sujay, Assigned: Joe Francis)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
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

Updated

19 years ago
Assignee: kostello → buster

Updated

19 years ago
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

Comment 1

19 years ago
the code should be clever enough to detect that the <tag attribute=value> just
needs its value changed, not a whole new tag.

Updated

19 years ago
Severity: normal → minor
Priority: P3 → P4
Target Milestone: M11

Comment 2

19 years ago
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.

Updated

19 years ago
Summary: applying font multiple times gives multiple font tags in HTML code → applying font to adjacent text gives multiple font tags in HTML code

Comment 3

19 years ago
changing summary to reflect bug buster describes above

Updated

19 years ago
Depends on: 10778

Updated

19 years ago
Target Milestone: M11 → M12

Updated

19 years ago
Target Milestone: M12 → M15

Comment 4

19 years ago
M15

Comment 5

18 years ago
This sounds like a joe thing; eliminating excess nodes.
Assignee: buster → jfrancis
Status: ASSIGNED → NEW
(Assignee)

Comment 6

18 years ago
accepting bug
Status: NEW → ASSIGNED

Comment 7

18 years ago
P1 for M15 (focus area for Joe)
Priority: P4 → P1
(Assignee)

Comment 8

18 years ago
fixed
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
(Reporter)

Comment 9

18 years ago
verified in 4/6 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.