Errors in IE11 console when I dismiss the sidebar by clicking outside the "X" button.

In IE11, there are errors when I dismiss the sidebar by clicking outside it’s “X” button while it is shown.

Observed behavior

1. In IE11, there are errors when I dismiss the sidebar by clicking outside it’s “X” button while it is shown. This is not manifested in Firefox v76 or Chrome v81.

2. Another issue is that the IE11 debugger fires up and prevents further interaction to the page untill I click on the Continue button. I checked and the Debugger setting is Break on unhandled exceptions but I do not remember setting it.

Expected behavior

No errors must show when I dismiss the sidebar by clicking outside it’s “X” button.

User-facing consequences

With this error, a user cannot proceed in using Kolibri with IE11, specially if the Debugger setting above is the default.

Errors and logs

daemon.txt ie11-console-3.txt kolibri.txt

IE11 error/s in console.

...
HTML1300: Navigation occurred.
File: learn
HTML1500: Tag cannot be self-closing. Use an explicit closing tag.
File: learn, Line: 127, Column: 11
HTML1500: Tag cannot be self-closing. Use an explicit closing tag.
File: learn, Line: 128, Column: 11
HTML1500: Tag cannot be self-closing. Use an explicit closing tag.
File: learn, Line: 129, Column: 11
HTML1500: Tag cannot be self-closing. Use an explicit closing tag.
File: learn, Line: 130, Column: 11
HTML1500: Tag cannot be self-closing. Use an explicit closing tag.
File: learn, Line: 131, Column: 11
Kolibri Modules: kolibri.plugins.learn.app registered
TOPICS_TOPIC
SCRIPT5007: Unable to get property '$el' of undefined or null reference
File: kolibri.core.default_frontend-0.14.0b4.js, Line: 1, Column: 1579009

Steps to reproduce

1. Get the Kolibri Windows installer for v0.14.0-beta4 on BuildKite
2. Use a Windows 7 VM and setup 1 learner using IE11.
3. Login as that learner user and then show the sidebar.
4. Try to dismiss the sidebar by clicking outside of it’s window.
5. Notice the error shown in IE11 console, and also the Debugger is shown and the user cannot proceed.

Context

• Kolibri version: v0.14.0-beta4 on BuildKite
• Operating system: Windows 7 VM
• Browsers: Firefox v76, Chrome v81, and IE11
• Python: v3.6.8

[radinamatic]

Thanks for trying to replicate and confirm! It makes sense for the tester to keep the debugger open while testing, my concern was to see if there are any visible blockers for the end users. Let’s close this for now since it seems not extant on beta7, and reopen if you notice an actual end-user-facing consequences again.

[mrpau-richard]

@cpauya I can’t reproduce this issue on Windows 7 even if the console log shown I’m using Kolibri 0.14.0 beta 7 released No errors display on the console log when I do the test.