![]() Please let me know if any of this isn't clear or if there is more information we can provide that would be helpful. They appear to have been introduced in Moodle 3.8. These issues are not present at all in Moodle 3.7. However, once the initial lock up is done the error still shows up, but performance seems fine.) But there appears to be less impact on performance in Chrome. We don't see these problems at all when using FireFox ( Mac). We are also seeing these results in Chrome (Mac), where we are seeing some lock ups (e.g., the second or third heading change triggers it and locks up for a moment. (See attachment for stack trace results). In the Atto Toolbar for the description field choose `A` (Paragraph Styles) What follows are the steps to reproduce in Safari, and I've attached stack trace results that Safari gave. And then, you usually can't do anything in the browser for a couple seconds or more, until it unfreezes and returns you control. Selecting text, then selecting a color, one usually has to wait a couple seconds for the change to take place. This sluggishness seems to be especially prevalent when using the Font Color toolbar. Oftentimes, one has to wait a second or two for the change to take place. ![]() ![]() For example, when writing on a page, selecting some text, the selecting the Heading toolbar icon, we see a stutter in how Atto reacts. Moreover, you can managed to find the point that was causing the error by check the error details in the Chrome dev toolbar console, this will give you the. What we're seeing is unresponsiveness and lock-ups in Atto when using Safari. We just upgraded to Moodle 3.8, and we're seeing some rather major performance issues with the Atto editor when using the Safari browser. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |