Monaco Editor not Loaded if Accidentally Press <ESC>
Description of bug
If you accidentally press the <ESC> button while the Configuration Manager is open, reopening it does not show you the editor any longer. In some instances, I can't get it to reload without reloading the entire page.
Steps to reproduce
List the precise steps to reproduce the bug:
- Install and log into DNN 9,8,0 RC2 as a superuser
- Open the Configuration Manager and open any file
- Press the
<ESC>button. The persona bar will close. - Reopen the Configuration Manager without reloading the page.
Current behavior
The editor is either not loaded or no longer properly initialized. There's a black dot that I assume is a tiny version of the editor?
Expected behavior
The Config Manager opens at the same point that the end-user was at before accidentally pressing the escape key.
Screenshots
https://www.screencast.com/t/QSqw3k7W
Affected version
- [ ] 10.00.00 alpha build
- [X] 09.08.00 release candidate
- [ ] 09.07.02 latest supported release
Affected browser
- [X] Chrome
- [ ] Firefox
- [ ] Safari
- [ ] Internet Explorer 11
- [ ] Microsoft Edge (Classic)
- [ ] Microsoft Edge Chromium
We have detected this issue has not had any activity during the last 90 days. That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue. We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 14 days, the issue will be closed automatically. If new comments are are posted and/or a solution (pull request) is submitted for review that references this issue, the issue will not be closed. Closed issues can be reopened at any time in the future. Please remember those participating in this open source project are volunteers trying to help others and creating a better DNN Platform for all. Thank you for your continued involvement and contributions!
Still relevant and I've seen it happen in other ways too.
We have detected this issue has not had any activity during the last 90 days. That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue. We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 14 days, the issue will be closed automatically. If new comments are are posted and/or a solution (pull request) is submitted for review that references this issue, the issue will not be closed. Closed issues can be reopened at any time in the future. Please remember those participating in this open source project are volunteers trying to help others and creating a better DNN Platform for all. Thank you for your continued involvement and contributions!
Still relevant.
We have detected this issue has not had any activity during the last 90 days. That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue. We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 14 days, the issue will be closed automatically. If new comments are are posted and/or a solution (pull request) is submitted for review that references this issue, the issue will not be closed. Closed issues can be reopened at any time in the future. Please remember those participating in this open source project are volunteers trying to help others and creating a better DNN Platform for all. Thank you for your continued involvement and contributions!
Still relevant.