Awesome - To save some time in testing. When you say "not everything is ready" can you highlight what

I just tried to get the new version running, so stuff which has to be done (I guess the list is not complete):

• the height is broken
• the parameters needs a complete clean up
• I would like to activate some features like "inline formatting" (when you select a text the small tooltip with the format options)

@bembelimen you need to do this as custom element as the rest of the fields

Nice.

Just an FYI, I think there is path in the plugin XML file allowing that's used for the skins directory. This might need updating too as you've added /ui to the other paths

Just an FYI, I think there is path in the plugin XML file allowing that's used for the skins directory. This might need updating too as you've added /ui to the other paths

Yes, thanks, I updated it.

The next days I'll go through the parameters and fix this stuff. If someone want to help, feel free to submit a PR against my branch :)

Is it possible to add an Accessibility Checker plugin?

Is it possible to add an Accessibility Checker plugin?

Do you have a link to one?

Accessibility Checker plugin

Thx, it seems that it is a paid plugin?

@zwiastunsw that plugin is neither free of cost or free to use

Sorry, in fact...

@bembelimen you do realise that the builder is based on a script (jQuery-ui) that is deprecated and marked for removal in J4? The builder needs to be redone based on dragula.js as the rest scripts in J4...

The builder needs to be redone

this is a separate task, no need to mix everything here,
to keep stuff simple and easier to test

Can you add Autosave plugin?
https://www.tiny.cloud/docs/plugins/autosave/

Full screen broken button joomla.

@bembelimen you do realise that the builder is based on a script (jQuery-ui) that is deprecated and marked for removal in J4? The builder needs to be redone based on dragula.js as the rest scripts in J4...

Done

When I use patchtester I get

The file marked for modification does not exist: build/build-modules-js/init.es6.js

com_patchtester does not work with anything that changes UI assets in 4.0 (anything in the build folder). If you see the "NPM Resource Changed" label on a pull request then don't waste your time trying.

@mbabker thank you. I assume it's not as simple as uploading the files to the right folder?

If you can get a copy of the compiled asset tree with the changes from this PR then you can upload that. But it's not as simple as uploading the build directory to a 4.0 installation.

Step 1. I'm downloading a copy of the branch from the Github of the author of the PR (for ex. https://github.com/bembelimen/joomla-cms/tree/tinymce-5.0)
Step 2. Next I unpacking in the document folder on a local server
Step 3. I'm running a Composer in this folder (composer install).
Step 4. I'm running a NPM in this folder (npm install)
Step 5. I'm installing Joomla

I have tested this item ✅ successfully on b3bfa55

Works for me

I have tested this item ✅ successfully on b3bfa55

Works for me

Thank you @bembelimen

Indeed thankyou!