RTC NPM Resource Changed bug PR-5.4-dev Pending

User tests: Successful: Unsuccessful:

avatar Fedik
Fedik
14 Feb 2026

Pull Request resolves #46738 .
Alternative to #46852

Summary of Changes

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.

Testing Instructions

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.

Actual result BEFORE applying this Pull Request

For all tests the editor is unusable in Firefox Developer edition, infinity reload.
Other browsers works good.

Expected result AFTER applying this Pull Request

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.

Link to documentations

Please select:

  • Documentation link for guide.joomla.org:
  • No documentation changes for guide.joomla.org needed
  • Pull Request link for manual.joomla.org:
  • No documentation changes for manual.joomla.org needed
avatar Fedik Fedik - open - 14 Feb 2026
avatar Fedik Fedik - change - 14 Feb 2026
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 14 Feb 2026
Category JavaScript Repository NPM Change
avatar richard67
richard67 - comment - 14 Feb 2026

@korenevskiy @OctavianC @muhme As you had tested the other PR #46852 , could you also test this one here?

avatar richard67 richard67 - change - 14 Feb 2026
Title
Fix TinyMCE init to work in Firefox Developer edition
[5.4] Fix TinyMCE init to work in Firefox Developer edition
avatar richard67 richard67 - edited - 14 Feb 2026
avatar korenevskiy
korenevskiy - comment - 15 Feb 2026

Great, everything is working.
I checked Firefox Developer 148.0 b15 (64x) Windows 11 Pro
πŸ‘πŸ‘πŸ‘πŸ‘πŸ‘

avatar muhme
muhme - comment - 15 Feb 2026

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?

avatar muhme muhme - test_item - 15 Feb 2026 - Tested successfully
avatar muhme
muhme - comment - 15 Feb 2026

I have tested this item βœ… successfully on db71366

Tested with JBT on macOS Intel

  • Before PR, it is sufficient to install β€˜Blog Sample Data’ and open an article for editing in Firefox Developer Edition to see the flickering display and the endless content loads. And this problem does not occur in Firefox, Safari, Chrome or EDGE.
  • Applied PR with Patch Tester and npm run build:js
  • No display flickering and the endless content load in article edit view in Firefox Developer Edition
    • Changing article content, toggling Editor, save is working
    • Created editor custom field and with Firefox Developer Edition it is possible to edit and save articles Editor custom field
  • Tested Firefox, Safari, Chrome and EDGE with editing article, toggle Editor, save and editing Editor custom field

This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46889.
avatar korenevskiy
korenevskiy - comment - 16 Feb 2026

πŸ‘ 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

avatar korenevskiy
korenevskiy - comment - 16 Feb 2026

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.
image

avatar OctavianC OctavianC - test_item - 16 Feb 2026 - Tested successfully
avatar OctavianC
OctavianC - comment - 16 Feb 2026

I have tested this item βœ… successfully on db71366

Windows 11 Pro:

  • Firefox Developer 148.0b15 (64-bit) βœ…
  • Firefox 147.0.3 (64-bit) βœ…
  • Chrome Version 145.0.7632.76 (Official Build) (64-bit) βœ…
  • Edge Version 145.0.3800.58 (Official build) (64-bit) βœ…

Mac:

  • Firefox 147.0.3 (64-bit) βœ…
  • Safari 17.6 βœ…

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.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46889.

avatar muhme muhme - change - 16 Feb 2026
Status Pending Ready to Commit
avatar muhme
muhme - comment - 16 Feb 2026

RTC


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46889.

avatar richard67 richard67 - change - 17 Feb 2026
Labels Added: RTC NPM Resource Changed bug PR-5.4-dev
avatar richard67 richard67 - change - 17 Feb 2026
The description was changed
avatar richard67 richard67 - edited - 17 Feb 2026
avatar richard67 richard67 - change - 17 Feb 2026
The description was changed
avatar richard67 richard67 - edited - 17 Feb 2026
avatar richard67 richard67 - change - 17 Feb 2026
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
avatar richard67 richard67 - close - 17 Feb 2026
avatar richard67 richard67 - merge - 17 Feb 2026
avatar richard67
richard67 - comment - 17 Feb 2026

Thanks @Fedik for this PR, and @muhme , @korenevskiy and @OctavianC for testing.

Add a Comment

Login with GitHub to post a comment