@ciryaquen: It appears not to be just a Mac or linux thing.
I’ve been trying to get my arms around this for a while now. Earlier today, I tried #2 you mentioned above and tested in MSIE6 and FF1.5 in Win XP Pro SP2. (I already use method #1).
Here’s what I tried –
this.defParam("force_br_newlines", true);
this.defParam("force_p_newlines", false);
this.defParam("convert_newlines_to_brs", true);
this.defParam("remove_linebreaks", false);
this.defParam("verify_css_classes", false);
this.defParam("verify_html", true);
this.defParam("apply_source_formatting", true);
this.defParam("inline_styles", false);
this.defParam("trim_span_elements", false);
this.defParam("convert_fonts_to_spans", true);
this.defParam("font_size_classes", 'fontSize1,fontSize2,fontSize3,fontSize4,fontSize5,fontSize6,fontSize7');
this.defParam("font_size_style_values", '');
this.defParam("doctype", '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">');
this.defParam("table_inline_editing", false);
this.defParam("fix_list_elements", true);
this.defParam("fix_table_elements", true);
FMI, here’s the link to the moxiecode reference for the configs above:
http://tinymce.moxiecode.com/tinymce/docs/reference_configuration.html
The doctype default was set to html 4.0…? and not even with a DTD using a URL.
But nothing above helped. I also modified the this.defParam("valid_elements",""); to allow better xhtml markup.
I wonder if the tiny_mce_gzip.php plays a role, but I can’t find any documentation about the changes made to it for the port to WP and what role it plays.
My main complaint is the RTE html source editor and the non RTE editor would change my html to use </p> without the opening tag instead of the <br /> I wrote. And it would try to wrap everything into a paragraph.
Now after the changes I made to tinymce, it doesn’t try to wrap everything in a <p></p> but uses my source div’s as a container for text.
For example, assume I have a container div and I want to insert text following the opening div tag. Before changes to the tiny_mce.js file, I’d get this garbage with and without the RTE on
<div id="CSS-P">
Text for testing </p>
<h2> blah blah h2 header</h2>
[other code...]
</div>
With RTE on TinyMCE changes the html source like this after uploading the modified tiny_mce.js
<div id="CSS-P">
<div id="CSS-P">Text for testing</div>
<h2> blah blah h2 header</h2>
[other code...]
</div>
when the correct source should be
<div id="CSS-P">
<p>Text for testing</p>
<h2> blah blah h2 header</h2>
[other code...]
</div>
Right?
The site I’m working on validates because I stopped using <br /> or empty <p> </p> while pasting my code into the “non” RTE form – they’re not well-formed xhtml in the strict sense anyway. It just means more CSS.
While pasting my html into the “non” RTE is ok for me to develop the blog’s initial look and feel, when the end-user gets it and edits pages, creates new posts, and etc., it appears that the Rich Text Editor, will make a mess of the code.
Worse case is it disrupts the layout and accessibility.
