hi all...
Because of the different synthax FF/IE
FF : <span style="text-decoration:underlin">
IE : <u>
A texte created via FF, cannot be edited via IE, for exemple, if you underline a word with FF, this word cannot be un-underlined via IE.. It is so with many different things like Bold/italic.
What can I do ? How can I force the FF style to be used and not the depreciated IE tags ?
Because of the different synthax FF/IE
FF : <span style="text-decoration:underlin">
IE : <u>
A texte created via FF, cannot be edited via IE, for exemple, if you underline a word with FF, this word cannot be un-underlined via IE.. It is so with many different things like Bold/italic.
What can I do ? How can I force the FF style to be used and not the depreciated IE tags ?
RE: BUG Firefox text cannot be edited via IE
You can on the other side change the code that Firefox uses, as it is as bad use <u> or <span style="text-decoration:underline"> because both are applying an style directly instead of relying on an external CSS to do the styling of the file.
RE: BUG Firefox text cannot be edited via IE
(with IE, in the editor the word is underlined, but when I use the same content on my website wich has another doctype it is not).
the <span style="...."> is underlined correctly in IE and in FF. That's why I prefer this method !
RE: BUG Firefox text cannot be edited via IE
Alfonso said it best. Keep style seperate from content, if possible.
Sometimes it's not. Within FCK it's possible to create styles and apply them vs. using the built in bold/etc. buttons. That's probably "best" I guess.
On the other hand, people may cut-n-paste, or whatever, and you'll still see them pop up.
Really the only way to be sure your content is formatted the way you want it is to parse it prior to saving (or loading). Do a search and replace for <u> and replace it with <span style="blah"> (or better yet, <span class/id="blah"> .
Regular expressions are a nice way to do it, so long as you're sure the markup is valid -- tags have matching closing tags, etc.(which it should, after loading it in the editor).
So probably parse your content just before you save it, formatting it the way you want. Not a bad idea anyway, if the input field is in a public place.
Sorry no easy answer, this is just one of those browser things: workaroundable, but not optimal. Give it time... we'll see what IE7 brings to the picture now as well. Please please let it be better than 5...