Next Curriculum editor bugs

figured we need to track known bugs with the new editor. A few are listed below:

1. If there is not enough code below an editable region, the editable region (upper and lower jaw) does not shift up toward the top of the editor. I believe it was discussed in a Front 3 meeting that there is a config setting that allows scrolling up when there are not extra lines at the bottom.

1. Sometimes when clicking the Reset All Tests button, the application crashes. So far, it has been difficult to duplicate the issue consistently.

2. When the --fcc-editable-region-- is on the first line and the seed is empty it produces the following error:

Error in function toStartOfLine in ./src/templates/Challenges/classic/Editor.js:123
Cannot read property 'setStartPosition' of null TypeError:
Cannot read property 'setStartPosition' of null at toStartOfLine (webpack-internal:///./src/templates/Challenges/classic/Editor.js:170:16) at preventOverlap

1. To reproduce this issue:

• Go to a challenge with code inside and outside the editable region
• Delete lines from within/outside editable region, until code is on a single line
• https://github.com/freeCodeCamp/freeCodeCamp/issues/39348#issuecomment-853880345 for more info

This issue might appear when the editor’s decoration (the upper jaw) goes below the first line.

Suggestion:

1. Add the “download your code” feature?
2. removing normalize.css https://github.com/freeCodeCamp/freeCodeCamp/issues/39348#issuecomment-876464606

[ojeytonwilliams]

I think, tentatively, that these are all fixed now, at least in the latest PRs.

Once https://github.com/freeCodeCamp/freeCodeCamp/pull/43777 and https://github.com/freeCodeCamp/freeCodeCamp/pull/43728 are in, I think this can be closed. Then we can just open single issues as and when new bugs are discovered/created.

[ojeytonwilliams]

@Sembauke no need, Tom’s right that the migration caused the bug. I’ve been looking into it and should have a fix before too long.