Editor adding unwanted styles

[D3]

I just installed the 2.2 version on a client site and have ran into an issue.

When I load a page into the editor, an unwanted span tag is being automatically inserted.

This is the code before loading:

Code:

<P><FONT size=+1><STRONG>Schedule:</STRONG></FONT></P>

This is the code that appears automatically, after loading, before even starting to edit:

Code:

<p><span style="font-size: xx-small"><strong>Schedule:</strong></span></p>

The font and strong tags have been removed and a span with a really tiny style has been put in its place.

AFAIK, this did not happen in the 2.1.1 version.

I can handle this with no problem but my clients have no idea how to deal with it.

Thanks,
Dan

[admin]

Hi Dan,

The old font tag is being replaced with the span, because the font tag is not XHTML compliant and the editor only outputs XHTML compliant code.  (So it has to convert the font tag to a span with font style.)

It's definately strange that it is replaceing the +1 size with a different value, though.  I'm going to look into this and figure out what that's happening.

[admin]

For reference, here's my post on the editor's vendor forums:

http://tinymce.moxiecode.com/punbb/viewtopic.php?pid=11533#p11533

[Jenkinhill]

It's definately strange that it is replaceing the +1 size with a different value, though. 

If I recall correctly font size +x or -x were included in HTML3.2 but were depracated in HTML4.0, and non-existent in XHTML, so the editor may not "know" what to replace old markup with. XHTML has been the standard for 6 years now, so there should not be too many such problems, but it would be good if somehow the editor said"I don't recognise this code, what do you want to do?" - or similar. 

I wonder what it would do faced with <blink>...........

[admin]

Kelvyn, you're probably exactly correct.

However, I'm going to push the tinyMCE developers to add a "switch" or flag so that it will preserve unknown values.  The code won't then be truly XHTML compliant... but of course that would only be true if the "incoming" code was already not XHTML compliant.