You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the H5P drag and drop response question type, the "answered" event seems to get swallowed and not properly emitted. This results in the resource never being marked as completed, even when all questions are correctly answered.
This appears to be related to the debounce behaviour that I added (in my wisdom) to our H5P event logging. I had observed in initial testing that H5P tended to rather prolifically log certain kinds of events, including "answered" - it seems that this debouncing is actually preventing them being logged at all.
I think the simplest solution here would probably be to remove the debouncing all together - or maybe as a half way, to remove it from the "answered" event - as "interacted" is far more common, and we don't use it anywhere for progress tracking.
If that solution doesn't work, then falling back to removing debouncing completely will be warranted.
Expected behavior
All H5P types should properly handle the answered event, and allow the progress calculation to set it as complete.
Steps to reproduce
This was specifically discovered within an unlisted channel, so I won't share the token here, but internal team members can reach out on Slack for details.
Context
Kolibri: 0.17+
The text was updated successfully, but these errors were encountered:
Observed behavior
When using the H5P drag and drop response question type, the "answered" event seems to get swallowed and not properly emitted. This results in the resource never being marked as completed, even when all questions are correctly answered.
This appears to be related to the debounce behaviour that I added (in my wisdom) to our H5P event logging. I had observed in initial testing that H5P tended to rather prolifically log certain kinds of events, including "answered" - it seems that this debouncing is actually preventing them being logged at all.
I think the simplest solution here would probably be to remove the debouncing all together - or maybe as a half way, to remove it from the "answered" event - as "interacted" is far more common, and we don't use it anywhere for progress tracking.
If that solution doesn't work, then falling back to removing debouncing completely will be warranted.
Expected behavior
All H5P types should properly handle the
answered
event, and allow the progress calculation to set it as complete.Steps to reproduce
This was specifically discovered within an unlisted channel, so I won't share the token here, but internal team members can reach out on Slack for details.
Context
Kolibri: 0.17+
The text was updated successfully, but these errors were encountered: