Regression with Chrome 73 in Typo3 7.6.32

[foppelfb]

Effect of the Problem:
When viewed in a Chrome 73 (MacOS Version 73.0.3683.46 (Official Build) beta (64-bit)) the RTE displays an empty raw HTML Document.
The Javascript Console does not throw an error, last message pertaining the RTE is:
[HTMLArea.Editor::onFrameworkReady]: Editor ready.

Chrome 72 works as expected, so do recent Firefox and Safari

[ohader]

Confirmed in TYPO3 v8 as well...

[pschriner]

For some reason chrome never loads the resources

When debugging (chrome://net-internals) I get

{"params":{"description":"","error_code":"8 (CANCEL)","stream_id":863},"phase":0,"source":{"id":13650,"type":9},"time":"112707070","type":191},

Which is not really helpful

[kkugelmann]

+1 here

[Geddo]

+1
Breaks my RTE on 6.2 LTS and 7.6 LTS
no problem with 8.7.24 so far

[amtmich]

+1 - same in 6.2 LTS

[andreasberniczki]

Same problem with 7.6 LTS

[bmack]

Thanks for the reports. I will see how time fits to fix this for RTEHtmlArea + TYPO3 v8. However, this repository only supports RTEHtmlArea for TYPO3 v8 LTS, so any issues regarding TYPO3 Core 6.2 and 7.6 won't and can't be addressed here, as the code base of the extension has changed since TYPO3 6.2/v7 (e.g. no ExtJS anymore).

If you have an active ELTS for TYPO3 v6.2/v7, there is a fix underway for the included RTEHtmlArea as well AFAIK. If you don't have ELTS, now is a good time to evaluate this https://typo3.com/products/extended-support.

[guppy42]

To fix it for chrome 73:

Open the editor file:
for 6.2 it's /typo3/sysext/rtehtmlarea/htmlarea/htmlarea.js
for LTS 7 it's /typo3/sysext/rtehtmlarea/Resources/Public/JavaScript/HTMLArea/Editor/Editor.js

locate the line that says;

src: UserAgent.isGecko ? 'javascript:void(0);' : (UserAgent.isWebKit ? 'javascript: \'' + Util.htmlEncode(this.config.documentType + this.config.blankDocument) + '\'' : HTMLArea.editorUrl + 'Resources/Public/Html/blank.html')

and change it to

src: UserAgent.isGecko ? 'javascript:void(0);' : (UserAgent.isWebKit ? 'about:blank;' : HTMLArea.editorUrl + 'Resources/Public/Html/blank.html')

That's it - 6.2 seems to automatically notice the file has changed and creates a new merged file containing the change.

In 7.2 the file gets served with ?bust=..... meaning if your server asks clients to cache JS for x days it will be a while before the change reaches them.

Any idea how I can forcibly change this bust value?

[thegass]

8.7 picks up the change instant.
fix seems to work for 8.7

[andreaskienast]

Many thanks to @guppy42, I was fiddling at the same line and wondered what happens here. I will create a PR for this.

[guppy42]

Seems the only way to change the ?bust= is to either go into development mode or alter the typo3 version
TS_7/typo3/sysext/core/Classes/Core/SystemEnvironmentBuilder.php:88: define('TYPO3_version', '7.6.32');

should be safe, but do so at your own peril ;)

[kevinlieser]

Worked – thanks a lot!

[hkarvasonis]

Thanks a lot for the fix! That worked as expected.