Firefox Problem: Invisible text cursor when replying to an HTML message

[cober]

When replying to an HTML message there is no text cursor visible in the html editor field. Nevertheless, it is possible to type a message. In order to make the text cursor visible, it is necessary to focus on another input field (e.g. by clicking into the recipients field) and focusing back to the message body input field.

This problem was observed with FF 3.6 (with IE8 it did not occur).

"Composing Messsages" settings to reproduce the problem:

• "Compose HTML messages"
• "Start new message above original"
• "Place signature above the quote"
• "When replying remove original signature from message"

I observed that by unchecking the "When replying remove original signature from message" option the problem is gone (i.e. the text cursor is visible from the beginning).

[sf_basilix]

I have confirmed this behavior consistently in Firefox (3.6.8) on Linux (Ubuntu 10.04, Lucid). This does not appear to happen for me in Windows XP SP3 with Firefox or IE.

[alec]

I'm unable to reproduce using svn-trunk (3909).

[backi]

same behavoir here with trunk 3909.
Cursors is invisible when I reply on (some or all -> I will check that) html messages.

[alec]

Please, check with newer revision.

[backi]

it still happens with trunk-[fa791286]. I checked some html messages and it doesnt appear at all html-messages. I think its when I reply to a "blocked images" html message, not sure about that, gonna test more later..

[backi]

just another note: if I switch to a differen tab in Firefox and back to roundcube, the cursor appears! strange.

[stinna]

I found that it's not only on mails with blocked images, but all reply mails in HTML; single and multiple recipients.

Interesting: If I click on a different text field (Subject, Recipients or even the Firefox Search field that I've switched on permanently), the cursor reappears when I re-click the body text field.

[Lazlo]

Can't reproduce with Roundcube 0.4.1 and Firefox 4 beta.

[alec]

Works for me too and because this looks like some strange unreproducable Firefox issue I'm closing it.

[subitus]

The 'invisible' bug still exists in [928bcaed].

• Reopen -

[alec]

Duplicate of #1487073