Did the update to the source editor break some features?
After the April release, one of my instructors commented the following changes when using the source code editor:
Cursor location:
- Previous behaviour: when you put your cursor somewhere in the Design view, then you switched to the Source Editor, your cursor appeared in the same spot.
- New behaviour: When you switch from Design view to Source Editor, in the Source Editor your cursor resets and appears at the top of the page. The instructor needs to scroll down through the HTML to put their cursor where they want it to appear.
Highlight tags:
- Previous behaviour: When you clicked in a tag, the source editor would highlight the open and close tags you were within.
- New behaviour: The tags do not highlight.
I'm not in the Source Editor often, so I don't know what the default behaviour used to be. I don't know whether to submit a bug or a PIE.
Answers
-
I have observed the same behaviour and it's a major inconvenience. We used highly customised HTML designs which make the code for various objects very hard to find if you have to start from the top of the code. It used to be that I could click on or near the object I wanted to edit, click the source code icon, and then be taken directly to the midst of the code I needed to edit.
It is also very useful to have the code editor highlight the start and the end of, say, a <div>.
It is very disappointing that D2L has decided to take away these very useful features, and perplexing that they would even think it a good idea to do so!
These changes will significantly compromise my efficiency, and the time taken to do tasks because now have to go hunting for things.
-
@Robert Daley thanks for confirming. I see you submitted https://desire2learn.brightidea.com/ideas/D9097 to fix the cursor issue, but it's marked as Closed. For some reason I can't see comments - do you know why it was closed? Are they going to fix it?
-
I also just saw that you posted https://desire2learn.brightidea.com/ideas/D9098: Any update on that one too?
-
Hi @Maureen Barrow ,
Thank you for reaching out to us within the Brightspace Community!
In an effort to best support you, I reached out to our product manager and they recommend logging this with your support desk. Please let me know if you require assistance with this and I am happy to connect you.
The changes made to the advanced code editor were done to allow for users with screenreaders to be able to use the editor which wasn’t previously possible. When a support ticket is created they will be able to investigate this further.
-
@Maureen Barrow This is a defect that they are looking into: https://community.brightspace.com/generic/s/question/0D55W000006NRPPSA4/there-was-an-update-overnight-to-the-brightspace-editor-there-seems-a-change-in-relative-positioning-when-going-from-wysiwyg-editor-to-source-code-editor-it-no-longer-places-your-cursor-in-the-same-relative-spot-was-this-intentional
