User tests: Successful: Unsuccessful:
Pull Request resolves #46738 .
Alternative to #46852
Fix TinyMCE init to work in Firefox Developer edition.
There some bug in this version of Firefox or in TinyMCE itself when iframe is in "in-completed" state after TinyMCE initialization.
Apply patch and run npm install (or install prebuilt package).
Test should be run in all browsers: Chrome, Firefox, Firefox Developer edition, and Safari would be good also.
Test 1) Open any article and try edit content.
Test 2) Create subform field with editor in it, add some content and then reorder subform rows.
For all tests the editor is unusable in Firefox Developer edition, infinity reload.
Other browsers works good.
Test 1) Editor works in all browser, content is editable.
Test 2) Before and After sorting the editors works in all browser, content is editable.
Please select:
| Status | New | ⇒ | Pending |
| Category | ⇒ | JavaScript Repository NPM Change |
| Title |
|
||||||
Great, everything is working.
I checked Firefox Developer 148.0 b15 (64x) Windows 11 Pro
πππππ
Great, everything is working.
@korenevskiy Thank you for testing π Could you please also test with multiple browsers and count the test result in our issue tracker?
I have tested this item β
successfully on db71366
Tested with JBT on macOS Intel
npm run build:jsπ Microsoft Edge 144.0.3719.115 (64x) Windows 11 Pro
π Firefox 147.0.3 Android 10
π Chrome 138.0.7204.157 Android 10
π Chromium 142.0.7444.107 Android 10
π Firefox Developer 148.0 b15 (64x) Windows 11 Pro
Great, everything is working.
@korenevskiy Thank you for testing π Could you please also test with multiple browsers and count the test result in our issue tracker?
I don't have access to this page, so there may be a regional Internet lockdown.
Nothing else is loaded from this page.

I have tested this item β
successfully on db71366
Windows 11 Pro:
Mac:
The Mac I've tested this with is an older Mac Mini with an Intel i5 so any looping code is more obvious - after dragging an Editor Field it takes a few seconds for the content to appear (the editor is loaded but it's blank). Can live with that as my initial problem was article editing being unresponsive (and any editor present on the page would eat up the memory due to the constant reinitialization).
While extensively testing #46852 (to compare it against this PR) I ran across a bug where if I drag and drop the Fields a few times I get an unresponsive editor (the one that was dragged) on Firefox - so far, this PR seems to work better.
| Status | Pending | ⇒ | Ready to Commit |
RTC
| Labels |
Added:
RTC
NPM Resource Changed
bug
PR-5.4-dev
|
||
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-02-17 21:26:45 |
| Closed_By | ⇒ | richard67 |
Thanks @Fedik for this PR, and @muhme , @korenevskiy and @OctavianC for testing.
For reference: https://bugzilla.mozilla.org/show_bug.cgi?id=2019320
For info, Firefox standard edition version 148 was released on 26 February 2026, and issue happens from J4 to J6 without this patch.
This PR fixes it for all J versions.
If you need to fix your site now and not wait for the next Joomla releases then I have made a hotfix available for you to download and use. It contains the exact same fix as in this Pull request it just saves you compiling the script etc https://github.com/brianteeman/tinymce-firefoxfix/releases
If you need to fix your site now and not wait for the next Joomla releases then I have made a hotfix available for you to download and use. It contains the exact same fix as in this Pull request it just saves you compiling the script etc https://github.com/brianteeman/tinymce-firefoxfix/releases
Hi Brian,
I've downloaded the two js files from your 'HotFix for J6' and I copied the files to the specified location, but the refresh continues. Should I do something else?
Tested on Joomla 6.0.3, Joomla 6.1.0 beta 1
Firefox 148 (64bit)
Windows 10 Pro
If you need to fix your site now and not wait for the next Joomla releases then I have made a hotfix available for you to download and use. It contains the exact same fix as in this Pull request it just saves you compiling the script etc https://github.com/brianteeman/tinymce-firefoxfix/releases
Hi Brian, I've downloaded the two js files from your 'HotFix for J6' and I copied the files to the specified location, but the refresh continues. Should I do something else? Tested on Joomla 6.0.3, Joomla 6.1.0 beta 1 Firefox 148 (64bit) Windows 10 Pro
@mariantanase It might need to clear browser cache, as in the opposite to a new release, the hot fix does not use a new version parameter when loading the script.
@mariantanase It might need to clear browser cache, as in the opposite to a new release, the hot fix does not use a new version parameter when loading the script.
I had the same problem on a 5.4.3 site, flushed the LiteSpeed cache on the server, cleared the cache in Joomla, cleared the browser cache, but still not good... Logging out and back in again then solved it for me.
the hot fix does not use a new version parameter when loading the script.
Visit: "System" => "Clear Cache" and delete "_media_version" or just use Delete All
Thanks @richard67 @HermanPeeren @Fedik
Is possible make a hotfix for v4?
Is possible make a hotfix for v4?
Yes, weβre working on a hotfix that will address this in 5.4.3 and 6.0.3.
Just to let you know, I just changed the tinymce files according for 4.4.14, using the same code as this PR, and is working so far.
open the address of the modified JS file in a new tab in the browser. Check if the file is fixed or not. It will be clear how to achieve a cache update on the server.
You can use an extension that specifically updates the cache of files.
https://github.com/webmasterskaya/joomla-reset-media-version
This extension adds a button to the Admin's home dashboard.
maybe the server itself caches the JS files. Since the directives are not specified in the JS file upload header
Clear-Site-Data: "cache"
https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Clear-Site-Data#syntax
The patch has a sligthly php error, double comments open.
Also breaks the layout in 2 rows in my Tinymce.
The patch has a sligthly php error, double comments open.
Should be irrelevant for the hotfix
Also breaks the layout in 2 rows in my Tinymce.
what you mean with this?
Just to let you know, I just changed the tinymce files according for 4.4.14, using the same code as this PR, and is working so far.
Hi everyone,
Sorry for posting here, I am not exactly the best programmer, but I can read a bit of code and I am trying to fix this issue for myself. I have a website that is still running on J 4.4.14 and I have the same issue, but the above mentioned approaches haven't worked for me. If I comment out the relevant lines in the TinyMCE.js file, nothing changes. If I replace the files with the fix that is meant for J5, I have no editor in the article anymore ( I see html code instead). As soon as I re-upload the old files, the editor is back, but so is the constant reload. Can anyone (please) give me a hint what to do?
Can anyone (please) give me a hint what to do?
Update to 5.4 or 6.0. 4.4 is unsupported since half a year.
Can anyone (please) give me a hint what to do?
or switch browser
or use a version of firefox as old and unsupported as your version of joomla
Can anyone (please) give me a hint what to do?
Update to 5.4 or 6.0. 4.4 is unsupported since half a year.
I am aware of this and the update will happen eventually, but the specific website has some tailor made features that are not compatible with 5.4, so it will take some time.
I was hoping to find an easy fix for the meantime, especially since @carlitorweb mentioned it worked for him, but I guess "switch browser" is the solution.
Can anyone (please) give me a hint what to do?
Update to 5.4 or 6.0. 4.4 is unsupported since half a year.
I am aware of this and the update will happen eventually, but the specific website has some tailor made features that are not compatible with 5.4, so it will take some time.
I was hoping to find an easy fix for the meantime, especially since @carlitorweb mentioned it worked for him, but I guess "switch browser" is the solution.
Did you remove the .min file? Is just a hotfix until we update Joomla. I will send later the modified file I have that worked for me, maybe can be useful for you.
Did you remove the .min file?
The .min.js file and the .min.js.gz file.
I deleted all 3 files, tinymce.js tinymce.min.js and tinymce.js.gz and replaced them with the files in the hotfix.
I didn't run any skripts or so, I just deleted the old files and uploaded the new ones.
I tried both versions (5.4 and 6.0) mentioned by @HLeithner and the download from @brianteeman
I went to System -> Clear Cache -> and deleted _media_version
Going back into an article, the editor is gone and I see html code.
@carlitorweb you wanted to send me some files?
I must be missing something simple.
I deleted all 3 files, tinymce.js tinymce.min.js and tinymce.js.gz and replaced them with the files in the hotfix.
I didn't run any skripts or so, I just deleted the old files and uploaded the new ones.
I tried both versions (5.4 and 6.0) mentioned by @HLeithner and the download from @brianteeman
I went to System -> Clear Cache -> and deleted _media_version
Going back into an article, the editor is gone and I see html code.
@carlitorweb you wanted to send me some files?
I must be missing something simple.
What you mean by "Going back into an article"?
also did you cleared your browser cache, just to be sure. it's also possible that a reverse proxy caches the old js files at server side.
With "going back into an article" I mean that I open an exisiting article where we have the issue with the flickering/reloading editor.
I was also wondering if it is a problem with the cache, but when I replace the files, the editor disappears and when I re-install the old files, the editor including flickering is back, so I guess that I have successfully cleared the cache, haven't I ?
Thank you for your support!
I wouldn't know how to do a screencast, I don't have any software installed with which I could record the steps. If there is a simple way, let me know. I could take screenshots if that is of any help.
My computer is a iMac M1 2021 with macOS Tahoe 26.1
Browser: Firefox 148.0.2
Joomla 4.4.14
ah ok joomla 4, we don't support joomla 4 any longer and it's possible that the new tinymce file is not compatible with the tnymce version is shipped in j4. I fear that will be a won't fix. But maybe someone come up with an solution.
What's the reason you don't update to j5/6?
edit: I overlooked the j4 comments where you already answered the questions.
The direct copy from Joomla 5 to Joomla 4 will not work.
However, in theory, it should be possible manually copy the changes from this PR.
Copy and replace section with if (!ed.inline) {....} to following code from joomla 5:
joomla-cms/build/media_source/plg_editors_tinymce/js/tinymce.es6.js
Lines 197 to 220 in a280811
in to media/plg_editors_tinymce/js/tinymce.js.
The .min.js and .min.js.gz versions need to be removed.
Copy and replace section with
if (!ed.inline) {....}to following code from joomla 5:
That worked!
Thank you!
Did somebody test if it works also for firefox on mobile devices. For me it doesn't on two different sites on mobile, desktop is fine. I still get the reloading.
Did somebody test if it works also for firefox on mobile devices. For me it doesn't on two different sites on mobile, desktop is fine. I still get the reloading.
I retested now, with 5.4.3 I am getting the reloading in Firefox 145.0.2 on Android 14. And it is fixed (no more releading) with the 5.4-dev branch, including this merged PR.
Thank you for your support!
I wouldn't know how to do a screencast, I don't have any software installed with which I could record the steps. If there is > a simple way, let me know. I could take screenshots if that is of any help.
My computer is a iMac M1 2021 with macOS Tahoe 26.1
Browser: Firefox 148.0.2
Joomla 4.4.14
I had the same problem, try this:
https://github.com/fab966/tinymce-firefoxfix-j4
@korenevskiy @OctavianC @muhme As you had tested the other PR #46852 , could you also test this one here?