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.
@korenevskiy @OctavianC @muhme As you had tested the other PR #46852 , could you also test this one here?