![]() I just know Atto is not up to what I need at the moment. I'm not quite up to the level of coding to even clearly identify the problems and the source of the problems. Says 'fixed' but there are some cases where I think it is not.The 'sanitising' seems to have unexpected consequences. However, most of us expect to communicate in text or message windows with rich text editing features such as bold, italic, color, and specific font usage. For example, you can use one to add a quick note or a service request. ![]() All of the buttons in Atto are implemented as Moodle subplugins. The plain text editors that most APIs provide are fine for some purposes. I already created a content-editable div, but I dont know where to look next. For example: if the cursor is within a ul-tag in my text-editor, only button li should be displayed. The challenge for me is: the buttons above my text-editor should be adjusted on the content of the DOM. Most of the code is written in JavaScript using YUI modules. I would like to create a simple text editor in Javascript. It is the default text editor in Moodle from 2.7 onwards, and is implemented as a standard Moodle text editor plugin. Ryan has responded here: saying "As Mark mentioned above, if you're using the WYSIWYG view on the atto editor the code behind the scenes will attempt to sanitise a few things in the content that you're pasting in an attempt to keep consistent styling (depending on where you are copying the content from, it can come along with a lot more information than what you see in the page)" There seems to be a clear indication that Atto is 'not supposed' to do all the things we might like. Atto is a JavaScript text editor built specifically for Moodle.
0 Comments
Leave a Reply. |