Bug #16570
closedProblem in Code View in Firefox 1.5.0.7
0%
Description
I saw this on the mailing list:
"I just upgraded Firefox on Win XP to version 1.5.0.7. In TYPO3 4.0.1 when
selecting code view in rtehtmlarea 1.3.7 the browser crashes."
I have the same problem in the same FireFox version on the Mac OS. I upgraded to latest rtehtmlarea 1.4.2 and still the same problem on both Intel & PowerPC Macs running Tiger 10.4.7. Taking FireFox back down to 1.5.06 fixes the problem
I also downloaded Camino and had the same problem.
(issue imported from #M4238)
Updated by Michael Stucki about 18 years ago
Cannot check this since I still run 1.5.0.6, but according to various newsgroup feedbacks, the bug seems reproducable.
There may be two reasons for it:
a) It's a bug in Firefox and will be changed in 1.5.0.8
b) Some functionality had to be changed (e.g. for security reasons?) and now doesn't work anymore.
Can anyone have a look at this please?
Updated by Marc Bastian Heinrichs about 18 years ago
I can confirm this problem with FF 1.5.0.7 on Win2000
Updated by Oliver Klee about 18 years ago
Has this bug already been reported in the Mozilla bug tracker?
Updated by Rudy Gnodde about 18 years ago
The problem also seems to occur switching tabs with tab dividers. There was an RTE in the first tab, so it could be related to that.
This seems to me a problem in Firefox, not TYPO3. A security update could disable something, but this should never result in a crash.
Updated by Ingo Renner about 18 years ago
I can confirm this on OS X 10.4.7, too. Downgraded to FF 1.5.0.6. But I guess it's more a bug of FF than of TYPO3
Updated by Michael Stucki about 18 years ago
We need to get an rtehtmlarea developer to look at it quickly.
Stanislas Rolland is currently on holiday so he won't look at this. If someone else has the time to debug this, it would be great.
Updated by Sven Haertwig about 18 years ago
It seems that the row 1144
this._iframe.style.display = "none";
in the file htmlarea.js is responsible for the crash.
Comment it out and click on the "htmlmode" button and you'll see that the textarea with the html source is shown below the wysiwyg view.
Updated by Jens Schmietendorf about 18 years ago
0010403 doesn´t work for me (WinXP Prof, FF 1.5..0.7),
FF chrashes anyway.
Updated by Sven Haertwig about 18 years ago
make sure you cleared your cache in firefox and you're using non compressed scripts. You can change this setting in the extension manager -> display shy ext -> htmlArea RTE.
You should also delete the temporary rtehtmlarea_* files in the typo3temp folder.
Just tried it with another website which is running on version 4.0.2
Updated by Marc Bastian Heinrichs about 18 years ago
FF also crashes when you do the following:
- edit an tt_news entry
- select tab "Relations"
- close the news
- edit the tt_news entry again
- crash (the view is now on tab "Relations" and rtehtmlarea is in the background)
Updated by Rudy Gnodde about 18 years ago
The problem does not seem to occur with a stand alone version of htmlArea. See http://www.dynarch.com/demos/htmlarea/examples/core.html if you want to test it yourself.
Updated by Urra about 18 years ago
Problem also occurs in TYPO3 4.0.2. I use htmlArea RTE v 1.4.2 (does not matter, because before I used the version of htmlArea that came with TYPO3 4.0.2 as default) and Firefox 1.5.0.7 on Windows XP.
Updated by Thomas Hempel about 18 years ago
I can confirm this with Ubuntu Dapper Drake. I don't use htmlarea but my browser crashes whenever I try to assign data elements to another element when it's a real mn-relation! ^^
Greets,
Thomas
Updated by Kirill Klimov about 18 years ago
Could confirm the problem when trying to switch to code view - browser crashes.
Have seen it on:
TYPO3 4.0, htmlArea RTE 1.4.1 (Local)
TYPO3 4.0.1, htmlArea RTE 1.3.7 (System)
TYPO3 4.0.2, htmlArea RTE 1.3.7 (System)
with FF 1.5.0.7
Updated by Kirill Klimov about 18 years ago
Also could confirm problem reported above by Marc Bastian Heinrichs:
(
- edit an tt_news entry
- select tab "Relations"
- close the news
- edit the tt_news entry again
- crash (the view is now on tab "Relations" and rtehtmlarea is in the background)
)
Have the same on
TYPO3 4.0, htmlArea RTE 1.4.1 (Local), tt_news 2.4.0
TYPO3 4.0.2, htmlArea RTE 1.3.7 (System), tt_news 2.4.0
with FF 1.5.0.7
And it is definitely deals with htmlArea, because in case if I use
"Disable Rich Text Editor (RTE)" checkbox - then there is no problem...
Updated by Kasper Ligaard about 18 years ago
I can confirm Firefox 1.5.0.7 and Firefox 2 RC1 crashes, Win XP Prof. SP2. So as Michael Stucki started stating: There might have been a change for security reasons(?) that has been aplied both FF 1.5 and the upcoming 2.0 release.
Digging into Talkback reports I found: http://talkback-public.mozilla.org/search/start.jsp?search=1&searchby=url&match=contains&searchfor=typo3&vendor=MozillaOrg&product=All&platform=All&buildid=&sdate=&stime=&edate=&etime=&sortby=bbid&rlimit=500
Moving on from there I found these bugs:
1) https://bugzilla.mozilla.org/show_bug.cgi?id=353473
2) https://bugzilla.mozilla.org/show_bug.cgi?id=313400
So it is on the Firefox 'radar',but will not get into Firefox 2.0 (as I understand).
Updated by Kasper Ligaard about 18 years ago
Good news: Explaining the situation to the Mozilla folks, they decided to include the patch, so the RTE will be fixed in Firefox 2.0 RC2.
I just downloaded todays english build, and now the RTE works again.
If, when FF2 RC2 are released, still expierence problems with the RTE it would be great if you voiced it in this bug.
Updated by Kasper Ligaard about 18 years ago
...and now the Firefox 1.5 branch has been patched. So the next update, FF 1.5.0.8, should correct the problem.
Updated by Andres Toomsalu about 18 years ago
I have tried this on all platforms (MacOSX, Linux, Win) and can confirm that switching RTE to source mode crashes Firefox 1.5.0.7 browser. I would consider that a major problem.
Updated by Michael Stucki about 18 years ago
Did you read the comments above? The issue was caused by a recent change in Firefox, and it has been fixed for the upcoming versions.
There is nothing we can change about this. Quick solution is to downgrade to Firefox 1.5.0.6 or wait for version 1.5.0.8. Additionally, the problem will be fixed in Firefox 2.0 final.
Many thanks for all who reported the issue to the Mozilla devs and helped to solve this quickly!