CK Editor not loading correctly

[simondate]

Expected Behaviour

CK Editior is not loading correctly meaning that 'TextArea' fields are not interactable

Also reported here in Gitter

Issue seemed to have been introduced in AAT 0.11.2. Likely an issue with a npm dependecy.

Issue can be fixed by just refreshing the page, but it's not really a great experience for the user!

[oliverfoster]

Can't replicate without further instruction.

[simondate]

I've only seen this once or twice myself, but a few of my clients who are using the AAT on a daily basis have reported it. The screenshot which I shared on that issue was originally shared by @nachocinalli, earlier the Gitter AT chat room.

I know that at the last minute we bumped the 0.11.2 release from using Node 12/14 to Node 16/18. My guess is that issue was tied to that?

Reproducing it is just random and only happens approximately every 1 in 4 times. Maybe there is some kind of race condition happening?

[oliverfoster]

Client side errors are very unlikely to be related to the server side architecture.
Here's the related issue on ckeditor: ckeditor/ckeditor4#4390

You're going to need to figure out how to replicate it. I can't. I therefore can't fix it.

Leaving open for the moment to provide an opportunity to supply replication steps.

[simondate]

Response from my client who reported this -

"Yes, it just seems to be random unfortunately. Mostly happens with ‘Text' or ‘MCQ’ components but not consistently."

Again, this does not seem to occur every time, so I appreciate it's not the easiest to debug. Perhaps someone else can provide input?

The issue shared on CKEditor's github seems to be fixed in 4.17.0 and we use 4.16.2, so it might just be as simple as updating the library?

I'm still curious as to why this only seemed to have started happening since the 0.11.2 release?

[oliverfoster]

You can see what changed here: v0.11.1...v0.11.2
As far as I can see, nothing that would explain the symptoms. I think it's highly unlikely that it's the cause.

It's more likely that it happened on v0.11.0 v0.10.5...v0.11.0 but that you didn't notice it until v0.11.2

[oliverfoster]

Try #2752 ?

[nachocinalli]

Switching to version 4.17.0 didn't work for me. The error persists, but I don't know how to debug it better.
Windows 11, Chrome, AAT 0.11.2, node 16.15.0.
Trying to edit a MCQ component.
I added a console.log in this file: modules/scaffold/backboneFormsOverrides.js

[oliverfoster]

Please try https://github.com/adaptlearning/adapt_authoring/pull/2752/files

You'll need to grunt build the client-side after making those changes.

[nachocinalli]

It worked! Thank you very much!

[oliverfoster]

Please approve the pull request #2752 @nachocinalli

[oliverfoster]

@simondate could you test and approve please?

[simondate]

I'm off work until Friday but can try then.

…

On Tue, 20 Feb 2024, 17:09 Oliver Foster, ***@***.***> wrote: @simondate <https://github.com/simondate> could you test and approve please? — Reply to this email directly, view it on GitHub <#2751 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMZKWYAFMSKFFR2P3UTAA3YUTKERAVCNFSM6AAAAABDQBBG7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJUGY3DOMJQHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>