IE Windows issue:

On some posts (but not all), I am seeing displayed within post bodies this:

'<!--[if !supportEmptyParas]--> <!--[endif]-->'

This appears between each and every paragraph. An example of this can be seen (in IE win) here: http://www.mediagirl.org/node/28

I see this on the lastest IE for win 98, and on IE5 for win NT. I do not see this on IE mac or any other browser on either platform. It seems that this conditional coding is not read properly by IE win.

IE Mac issue:

All posts seem to have short lines, as if the right-hand margin were very very large, starting with the second paragraph. (First paragraphs seem to be unaffacted.) (It was set for 3em in the CSS. I changed that to 20px, but that made no difference.) Looking at the source, the text is broken in display but there are no breaks or paragraphs coded to do this. I'm not sure what's causing this.

Again, this is only with IE Mac. IE win does not do this, nor do any other browsers I have for win or mac. An example of this can be seen here: http://www.mediagirl.org .

To be honest, this may or may not be an HtmlArea-related issue, as I do not know for sure whether these posts were displayed this way before installing the module. (Installing the module changed the formatting, mostly losing paragraph breaks, on all prior posts, immediately upon activiation of the module, so no previous posts can be assumed to appear exactly as they did before the module's activation.)

It could be IE just messing up on its own (which would not surprise me one bit). But I offer this here, just in case, especially given the ubiquitous nature of IE in the browsing world today. I hope these help.

Comments

gordon’s picture

gordon commented

I have taken a look at the example that you sent me, Now you are sure that it is HTMLArea that this causing this, as the example looks like you are cutting and pasting from a word document, or similar MS product. I say this because it has class="MsoNormal" all through the source, which is generally a sign that it came from Word.

media girl’s picture

media girl commented

I had not thought of that. I wondered where those codes came from. It is quite possible she composed first in Word. Does that mean the "kill word on paste" filter does not address these things? (It was enabled from the start.) Is this something I should warn people of when composing in Word?

Now that you've seen it, I will delete those codes. Thanks for the response.

gordon’s picture

gordon commented

Any HTMLArea js issues please send to www.htmlarea.com