http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692009-08-18T08:28:14ZTYPO3 ForgeTYPO3 Core - Bug #20896: rtehtmlarea crashes chrome-browser when utf-8 letters are usedhttp://forge.typo3.org/issues/20896?journal_id=663562009-08-18T08:28:14ZDavid Bruchmanndavid.bruchmann@gmail.com
<ul></ul><p>Take some text from here - I used the Text from inside meta-description prepended with "Newsbeitrag Text äöü ÄÖÜ ß ":</p>
<p><a class="external" href="http://support.microsoft.com/kb/298459/ar">http://support.microsoft.com/kb/298459/ar</a></p> TYPO3 Core - Bug #20896: rtehtmlarea crashes chrome-browser when utf-8 letters are usedhttp://forge.typo3.org/issues/20896?journal_id=663572009-08-18T09:00:43ZDavid Bruchmanndavid.bruchmann@gmail.com
<ul></ul><p>Bug is posted at google too:<br /><a class="external" href="http://code.google.com/p/chromium/issues/detail?id=19578">http://code.google.com/p/chromium/issues/detail?id=19578</a></p> TYPO3 Core - Bug #20896: rtehtmlarea crashes chrome-browser when utf-8 letters are usedhttp://forge.typo3.org/issues/20896?journal_id=663582009-08-18T09:21:48ZDavid Bruchmanndavid.bruchmann@gmail.com
<ul></ul><p>Doesn't occur in normal Text-Records but in tt_news-records</p> TYPO3 Core - Bug #20896: rtehtmlarea crashes chrome-browser when utf-8 letters are usedhttp://forge.typo3.org/issues/20896?journal_id=663592009-09-02T06:34:35ZStanislas Rolland
<ul></ul><p>I was able to produce a tt_content record that reproduces a similar issue. If the record opens on the tab containing the RTE-enabled field, Google Chrome 4.0.203.2 craches. If the record opens on another tab, switching to the tab containing the field allows to view the record without any problem. The problem does not appear in Safari 4.0.3. Nor does the problem appear with TYPO3 trunk (4.3)... Very hard to understand what is going on at the moment the browser crashes.</p> TYPO3 Core - Bug #20896: rtehtmlarea crashes chrome-browser when utf-8 letters are usedhttp://forge.typo3.org/issues/20896?journal_id=663602010-06-07T03:50:31ZStanislas Rolland
<ul></ul><p>Perhaps the issue was fixed in the browser. I am unable to reproduce this issue in Google Chrome 6.0.422.0 dev.</p>