you can drop jdragndrop and use TinyMCE image upload,

I tried something with custom images_upload_handler, but due to new media manager limitation, it not finished 4.0-dev...Fedik:image-drop , you can use that as a hint, if you like.

@Fedik the reason we didn't use the build in tinyMCE uploader was that it didn't support custom names (eg the name of the file for upload) back in version 4.0. I guess if this is changed in v5 (I'll have to check) then we can use it

Setting images_reuse_filename to true tells TinyMCE to use the actual filename of the image, instead of generating a new one each time.

Reading their docs this might be a limitation:

Anyways I can try to see if I can use their handler later today

Reading their docs this might be a limitation

images_upload_handler option can help to break through this limitation ?
you are free to copy Joomla.JoomlaTinyMCE.uploadHandler from my unfinished branch.

Nothing much critical, but would be good to use tinymce features, when it possible,
it also can display upload errors to user etc

So, using the tinyMCE's own handler is not that hard but there are some differences:

• The name is always lowercase
• There is versioning (the question mark..) even with the images_reuse_filename=true
• I can't find a way to append the attribute loading=lazy, although this should be doable with some more fiddling
• But the worse is that there are instances that the file(s) might be inlined, eg: tinymce/tinymce#5205
• Also there are still quite some issues in their side: https://github.com/tinymce/tinymce/issues?q=is%3Aissue+is%3Aopen+upload+image

@Fedik if you want to play around with this the code is here: https://gist.github.com/dgrammatiko/1ffc213290914024817a106fc9f5f89c

But the worse is that there are instances that the file(s) might be inlined

hm, I see, that not very good

upd. well then, leave the plugin ?

Adding the "Release Blocker" label since inherited from issue #27477 .

The image can be imported into the image folder via drag and drop. It is stored in images.

But the result in the artice is:
<p><img src="../images/xx.jpg" loading="lazy" /></p>

The alt="" is missing which is important for a11y
and the image is in src="images/ ... " not in "../images..."

But the result in the artice is: <p><img src="../images/xx.jpg" loading="lazy" /></p>

That's weird because the code is hardcoding to / as the first character:

https://github.com/joomla/joomla-cms/pull/28928/files#diff-3190d9429a056012da019775e53ad156R58

The alt="" is missing which is important for a11y

You can add it by clicking on the tinyMCE's image icon. By dropping an image we don't have any data to fill that attribute ;)

Why is leading slash used here?

Why is leading slash used here?

Essentially the code is copy paste from here:

Shouldn't the url start with a backslash?

PS maybe there were couple of mistakes there, updated to reflect the media field code

You can add it by clicking on the tinyMCE's image icon. By dropping an image we don't have any data to fill that attribute ;)

alt="" is all right. Then a screenreader reads nothing. If there is no alt alt all, the screenreader reads the filename - and every validation tool reports an error.

alt="" is all right

Empty alt attribute was added

Doesn't work. Getting this now:

TypeError: response.data.url is undefined plugin.js:58:13

@SharkyKZ should be fine now

I have tested this item ✅ successfully on 2024b22

Works!

I have tested this item ✅ successfully on 2024b22

RTC

Merging thanks. ?