Bug #40997
closedRTE 4.5: JS error in firefox
0%
Description
4.5.14 is the last version where the RTE will work in firefox, laterversions fails with "unlabeled break must be inside loop or switch".
[BE][DEBUG] stubbornly refuses to disable js compression but the error seems to come from
typo3/sysext/rtehtmlarea/htmlarea/htmlarea-gecko.js - diffing this file with the .14 version yields no changes however.
Given the volume of security updates in version since .14 this is really becoming an issue.
Updated by Oliver Hader about 12 years ago
- Status changed from New to Needs Feedback
- Priority changed from Must have to Should have
Hm, I could not reproduce this behavior with the Git version of TYPO3 4.5 (which is only 2 commits ahead of TYPO3 4.5.19).
So, can you please give further information on how to reproduce and where this problem happens (e.g. add some screenshots).
Thanks in advance!
Updated by Morten Haggren about 12 years ago
Oliver Hader wrote:
Hm, I could not reproduce this behavior with the Git version of TYPO3 4.5 (which is only 2 commits ahead of TYPO3 4.5.19).
So, can you please give further information on how to reproduce and where this problem happens (e.g. add some screenshots).
Thanks in advance!
Step by step (always reproducible )
- change typo3 symlink to point from 4.5.14 to 4.5.19
- Pick a firefox ( tested with ff on windows, linux & mac )
- log into typo3
- (optional) clear cache
- attempt to edit any page element with a RTE text editor
At this point the loading text on the rte never goes away - repeating the last step with the console open gives the error mentioned in the original post.
Tested it on 10 different 4.5.14 installations, in every case I get the above.
Updated by Jan Bartels about 12 years ago
Some (but not all!) of our users experience a similar effect with Firefox 15.0.1 and Typo3 4.5.19: The RTE isn't loading in BE. The Firebug-console shows "Error: throw $continue is deprecated, use return instead". FF has been started without any Plugins, a cleared cache and even a disabled virus scanner without success.
Personally, I cannot reproduce this behavior on my computer. The error message was reported by one of our users. I don't know if this is actually the same issue as the original of Morten, but it seems to be very similar.
Updated by Michael Theurich about 12 years ago
- the same problem occurs on Chrome and Safari, but it does work on IE
- I have language overlay pages. The editor works correctly when I start it on any of the translation content elements (why??)
- watching the AJAX loads in firebug, it seems as if many of the required resources are actually transferred, but then finally this list is truncated and a new POST request is retrieved. I could not manage to step through the loads and see where it goes wrong
- in addition to the error mentioned above, firebug shows syntax errors in the modernizr JS. but when you look at the JS, there is no such broken code as reported by firebug. could this be overlapping loads/decompress etc. actions?
please take a look into the issue, being forced to use IE for typo3 authoring is a pain.
Thanks
Updated by Urs Braem about 12 years ago
I have a similar issue. RTE is not loading in localized tt_news articles with Firefox 16. Works in IE 9 though.
RTE is not loading in Lang 0 - it works in Lang 1
JS Error thrown:
TypeError: HTMLArea.I18N is undefined
http://pro-velo.ch/typo3temp/compressor/htmlarea_cumulative_28a9d14f9695d173abdd_compressed-6c5f36b54ed3d9ddcbae2cb22c723873.js
Line 1
TYPO3 4.5.22 with (ah I see, old) tt_news 3.0.0 - maybe that's the cause.
We can't upgrade at the moment though to test if it goes away.
I'll post this anyway, maybe it's helpful
Updated by Thomas Mammitzsch over 11 years ago
had the same issue after updating an installation from 4.4 to 4.5. Happened only on german localized accounts.
Solved it by updating all translations via Extension Manager->Translation Handling.
Updated by Alexander Opitz over 11 years ago
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?
Does updating the language files resolves this issue?
Updated by Morten Haggren over 11 years ago
Alexander Opitz wrote:
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?
Does updating the language files resolves this issue?
My apologies for not updating this issue, I was unaware that the issue had been resolved internally - In version 4.5.25+ this is no longer a problem ( for us atleast ) 6.2 alpha2 works aswell - haven't tested 6.0 and 6.1 with firefox
Updated by Alexander Opitz over 11 years ago
- Status changed from Needs Feedback to Closed