Edit Post box empty in Firefox

[CJ]

Title says it all really. Using Firefox, I go to edit my ad and the box which should contain the original message is empty.
Works fine with Chrome.

Doctor, it hurts when I do this.............

And another thing. I get two notifications when I get a PM. While reading the message, I get another notification for the same message. No biggie, just odd.

Cheers

[mithrandir]

Chris, you get an empty edit box if the text contains symbols from a character set Firefox doesn't support. I see this happening all the time with posters who use Macs or European character sets. Spotting open/close curly quote marks is one give-away. En and em dashes are another. If the encoding was correctly recorded with the text it might work but that does not seem to be the case.

You could just use Chrome to reply to those messages if that works.

[CJ]

The only unusual characters in this case are the inch sign and a plus sign.

I used to use Chrome for all my browsing but when I reset my laptop it wouldn't install. I got used to Firefox. After a couple of weeks of downloading W7 updates Chrome did install. I guess I'll go back to using Chrome.
Cheers

[mithrandir]

If the inch sign is a left or right curly/sloped double quote Firefox will refuse to display any text.

The reply page has the meta tag "text/html; charset=ISO-8859-1". Curly quotes do not exist in that encoding. They do exist in Windows-1252.

You'd need some means of forcing Firefox to treat it as Windows-1252 until such time as Firefox implements the HTML5 requirement that ISO-8859-1 be treated as Windows-1252. I guess Chrome already does that.

Try "View > Encoding, West European (Windows)".

To the webmasters, can you add "accept-charset=utf-8" to the form for the text box and see if that makes any difference.

[iceman]

There's been no change to IIS at all, so it must be a problem with your version of Firefox?

[CJ]

My Firefox is set to update automatically. I'm using version 34.0.5
I really don't mind switching back to Chrome. I just thought you should know about that issue.
:thumbsup:

[sheeny]

Interesting comment, Andrew, thanks. I did notice this with one of my posts recently, and that was probably the cause. I worked around it with Chrome...

Al.