Inconsistent Output Based on browser being used.

[GoogleCodeExporter]

Using FF versus using IE produces different output in different situations
(<b> versus <  style="font-weight: bold;">)  

This causes a problem when you are trying to style the end result.  

in your css, you may have

b {
 font-family: Lucia;
 font-size: 120%;
}

If that is the case, you get VERY different results when using FF or IE.

However it appears that there is no way to insert a span with IEs
implementation of execCommand (from my limited understanding)

Original issue reported on code.google.com by issac.kelly on 5 Apr 2008 at 7:00

• Merged into: #26

[GoogleCodeExporter]

I am not entirely sure how it would work but perhaps it would be possible to 
allow a
plugin option to make jWYSIWYG to use the XML/CSS Parser that WYMEditor has?
(http://files.wymeditor.org/wymeditor/trunk/build/build/) Having it as a plugin 
would
keep the core code light.

Just a thought.

Original comment by brendonk...@gmail.com on 20 Apr 2008 at 2:48

[GoogleCodeExporter]

The problem is that jWYSIWYG uses the DOM implementation of the browser and as 
usual
all browsers use a slightly different implementation. but i don't like the idea 
of
being dependent on a another plugin. but i do agree that we need a better 
consistency

Original comment by N.Hen...@gmail.com on 6 Jan 2009 at 7:21

[GoogleCodeExporter]

The output should be basic xhtml markup without and span tags and inline css. 
Makes
it difficult to output saved jwyiswyg content in any cross-browser manner.

Original comment by see...@gmail.com on 20 Feb 2009 at 4:17

[GoogleCodeExporter]

After studing a lot of js editors, I can say the best way to make a consistent 
output, is to parse it with regex, but 
for this, you have to implement some kind of hook, beforeSave, that receives de 
iframe content, and in this, 
parse it. 
I see it working on moeditable, and now i make a litte plugin for punymce, to 
work as it. 

To parse have to consider three cases, explorer, mozilla and webkit.

Original comment by jor...@gmail.com on 28 Apr 2009 at 12:21

[GoogleCodeExporter]

Issue 67 has been merged into this issue.

Original comment by akzhan.a...@gmail.com on 8 Dec 2009 at 9:21

[GoogleCodeExporter]

Original comment by akzhan.a...@gmail.com on 8 Dec 2009 at 12:21

• Changed state: Duplicate