pxt-microbit
pxt-microbit copied to clipboard
microsoft
Errors loading the Beta editor
Describe the bug
The beta editor seems to work in an incognito window, but in some existing sessions it shows errors to multiple different people.
Some of the issues found with different browser sessions:
Carlos' computer Chrome
Trying to load an existing project from the front page:
https://makecode.microbit.org/beta
Trying to load the beta editor:
https://makecode.microbit.org/beta#editor
Same browser with the debug flag: https://makecode.microbit.org/beta?dbg=1#editor
Carlos' computer Edge
On the same computer with a different browser (which had used makecode and makecode beta before):
Jonny's computer Chrome
The experimental feature enabled was the accessible blocks
Katie's computer Chrome
Also accessible blocks experimental feature enabled.
@microbit-katie has found that disabling the accessible blocks experimental feature resolved the issue, so it looks like that might be the culprit.
I've tried this as well and it has fixed the session I had in Edge browser, but not the one I had in Chrome.
One problem though, after disabling the accessible blocks experiment the beta editor deletes all the blocks from your opened project and it saves it, essentially permanently deleting the user code.
While disabling the accessible blocks feature resolves the problem when the blocky toolbox and workspace don't load, the issue I still have where projects cannot be loaded at all, still persist.
I can leave this session as it is for the time being in case there is any diagnostic you'd like me to run (the ?dbg=1 flag doesn't seem to do anything). In this state all projects are inaccessible, but I can create new ones that work.
I've fixed the keyboard nav bug, just haven't bumped it to beta yet!
I'll look into the other bug...
Were you able to look into the other issue @riknoll ? I still have the beta session with broken projects, in case it's useful for debugging.
@microbit-carlos oh, no i wasn't able to repro this after fixing the keyboard nav so i assumed it was fixed. is this only an issue with projects you opened while the keyboard nav bug was still there? it's possible that the exceptions caused the project to save in a corrupted state.
Not quite, as it's not only with projects I tried to open with the keyboard nav experiment, but I believe with all existing projects that existed at the time, even the ones I didn't attempt to open.