In Moodle it is not possible to create a linked image with the ATTO editor. It is possible in Chrome, Edge, Safari. What is going on? Firefox is my default browser. Will I be forced to change?
Categories
(Core :: DOM: Editor, defect)
Tracking
()
People
(Reporter: p.vignol, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/114.0
Steps to reproduce:
I want to create an image with link.
Actual results:
In Moodle it is not possible to create a linked image with the ATTO editor. It is possible in Chrome, Edge, Safari.
Expected results:
the link on image should be easy to create in wysiwyg mode
|
||
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::DOM: Editor' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
(In reply to Philibert from comment #0)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/114.0
I want to create an image with link.
Could you provide more details on how you attempted to create the image? Did you use drag-and-drop, copy-paste, or ...?
It would be also helpful if you could provide a video that show the issue. Thanks!
To create an image with url link, I go through the ATTO wysiwyg editor.
I start by inserting an image.
The problem is when I want to insert a link on the image put in the editor. It is possible to do it in html but by the wysiwyg it is not possible. I've noticed this problem since Firefox 110, if memory serves. It works in Safari, Chrome, Edge.
On the other hand, when you want to put a url link on a word, it works.
|
||
Comment 4•2 years ago
|
||
Philibert, do you know of a running instance of ATTO where I could try this out? All of the live demo examples I've found for Moodle have been using TinyMCE, where this isn't an issue.
Unfortunately, I don't know of any instances where to test it. Under TinyMCE, it works well indeed. That's what I do.
On the other hand, for users, they usually use Moodle's default ATTO editor and don't think to change their editor type. This maneuver is complex for the uninitiated.
As I advise to use Firefox, it's annoying. Everyone tells me that in Chrome it works and I don't like it...
|
|
||
Comment 6•2 years ago
|
||
If you open the console, do you get any error messages that could give us a clue? (Right click -> Inspect -> select Console)?
No error message. Very strange!
The problem occurred with Firefox 107 or 108. Previously it worked fine.
|
|
||
Comment 8•2 years ago
•
|
||
Oh, so it's such a clear regression! Then there is a way for you to help us with more information, if you can then we can surely fix this bug. We have a tool called mozregression, which searches for when a build introduces a bug. If you're able to help us these are the steps you'd need to perform the following.
Download mozregression-gui from here: https://mozilla.github.io/mozregression/install.html alternatively if you have python you can just do pip install mozregression.
If you do the latter then you just need to run:
mozregression --good 100 --bad 110
since we know that Firefox 100 is surely good and Firefox 110 is surely bad from what you've noticed. Then this program will download Firefox versions in between and start them letting you test if the bug reproduces and then input if it was bad or good. This is actually quite a fast process and in the end it will give you a link that points to where the problem was introduced.
If you do the former the video at https://mozilla.github.io/mozregression/quickstart.html explains how it works, but it's basically the same: input the two versions which you know are good and bad, then let the program do the same as above.
I completely understand if this is too much to ask, but this will definitely give us the exact location where we introduced a breaking change.
Description
•