Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

<font> tags being inserted in corrected text in rich text environment (Gmail compose)

  • 2 odpowiedzi
  • 5 osób ma ten problem
  • 25 wyświetleń
  • Ostatnia odpowiedź od cor-el

more options

Since I believe ffox 16 (on both OS X and Win7), I've found that whenever I correct a misspelled word in a Gmail compose window using rich text — by backspacing and retyping — ffox will highlight *the retyped part of the word* as being misspelled. This has been driving me nuts. I've since tracked down the problem to the rich text environment within ffox itself, I think. Examining the original source of the email message in Gmail, you can clearly see the 'corrected' text in the MIME HTML encoded message, and using view selection source prior to sending. Firefox is inserting <font> tags at the point where I begin retyping! So my guess is the spell checker fails for the 'new' word, where it is not valid in its own right.

To illustrate, I wrote a simple new email with the text 'what is this nonsense', where 'this' and 'nonsense' were first misspelled (missing letter), then corrected by backspace and retyping. </font>

Since I believe ffox 16 (on both OS X and Win7), I've found that whenever I correct a misspelled word in a Gmail compose window using rich text — by backspacing and retyping — ffox will highlight *the retyped part of the word* as being misspelled. This has been driving me nuts. I've since tracked down the problem to the rich text environment within ffox itself, I think. Examining the original source of the email message in Gmail, you can clearly see the 'corrected' text in the MIME HTML encoded message, and using view selection source prior to sending. Firefox is inserting <font> tags at the point where I begin retyping! So my guess is the spell checker fails for the 'new' word, where it is not valid in its own right. To illustrate, I wrote a simple new email with the text 'what is this nonsense', where 'this' and 'nonsense' were first misspelled (missing letter), then corrected by backspace and retyping.

Wszystkie odpowiedzi (2)

more options

ah I see showing the output in Troubleshooting isn't very helpful. Repasting here.

view-selection source for corrected text:

<font face="arial,helvetica,sans-serif">what is th<font size="2">is nons<font size="2">ense<br><br></font></font></font>

the raw email text showing correct in plain but messed up in MIME HTML. I've tested this in Chrome and it does not produce the same result.

Content-Type: multipart/alternative; boundary=e0cb4e6ff8b54cdfe204cefcc779
--e0cb4e6ff8b54cdfe204cefcc779

Content-Type: text/plain; charset=ISO-8859-1
what is this nonsense

--e0cb4e6ff8b54cdfe204cefcc779

Content-Type: text/html; charset=ISO-8859-1
<font><font face="arial,helvetica,sans-serif">what is th<font>is nons<font>ense<br><br></font></font></font></font>

--e0cb4e6ff8b54cdfe204cefcc779--

Zmodyfikowany przez cor-el w dniu

more options

See:

(please do not comment in bug reports)