cancel
Showing results for 
Search instead for 
Did you mean: 

Static Toolbar for New Rich Content Editor

Static Toolbar for New Rich Content Editor

Because all of the important features for linking and adding documents have been moved from the sidebar in Canvas to the top of the Rich Content Editor, it would beneficial (and user-friendly) to have the toolbar remain static at the top of the screen when scrolling through the Rich Content Editor. As it is now, I scroll down to an area and want to add a link or attachment, but I have to scroll back up to reach these tools on the toolbar, which means I have to hope my cursor is still in the correct spot. Having the toolbar remain at the top of the Rich Content Editor, no matter where I scroll, would improve efficiency and ease of use.

Melissa Rasmussen

This idea has been developed and deployed to Canvas

For more information, please read through the Canvas Deploy Notes (2020-07-15) 

(6)
62 Comments
Lamplighter II

This is going to be a huge issue. I have a case ( 05148564) in about this issue. The case was marked solved today because support stated it is working as designed. I am sorry but this is NOT working for many of us.  Many people have already noted this issue in the new rich content editor release notes. Please fix this before we all have to use the new editor!

Community Advocate
Community Advocate

Agreed -- I don't understand why the new RCE text area increases in size instead of creating a scroll bar within the text area. I also view this as a bug and it shouldn't be considered FAD -- functioning as designed.

Explorer III

I agree with snugent‌ and jwadec‌, This is a huge issue and has seen me going back and forth between the old and new RCE just because scrolling up the page every time I need to add a link in a large is a pain and a waste of time.

It *feels* like the window is meant to be expandable, so I can't believe that this is actually considered FAD.

Explorer II

Agreed, this is very poor user experience. If not addressed now, the community will definitely voice their displeasure when this new RCE is forced and Canvas will be scrambling again as usual. If this isn't fixed by the time it's forced upon us, I'm going to again have to resort to one of my seeming 100s of Tampermonkey scripts to fix the underwhelming UI/UX of Canvas. The question that I always wonder about Canvas Instructure is "Are the people developing this product actually using and testing it?" Maybe the UI/UX designers should spend a day or two in our shoes and try to design a product while scrolling up and down a page constantly, over and over again. Talk about inefficient. Canvas, please take it from your actual users and not some generic testing plan that's automated...this...is...not...working...for...us.

This whole voting system and listening to the community is broken. I'd love to see the data, but I can't imagine that more than 1% of the canvas users actually see these ideas, does any kind of upvoting, or voices their concerns on community pages; yet they (Canvas) require an absurd amount of upvotes in order to actually consider an idea. This model essentially allows Canvas to present a facade that they are listening to user ideas and concerns; when in reality, they have full control in directing all development.

I've given up on spending time trying to advocate and upvote ideas; they're never seen. I go straight to the developers on github. This is where our voices are actually heard. I have had numerous successes with the developers on github if the problem is worded appropriately and has the appropriate argument.  

Perhaps this needs to be addressed from an accessibility standpoint since Canvas likes to tout how accessible they are. I promise you that this kind of user experience in the RCE is not accessible by any stretch of the imagination. Find the appropriate WAI-ARIA offense and this will gain much more traction. Two sites that might help: Authoring Tool Accessibility Guidelines (ATAG) Overview | Web Accessibility Initiative (WAI) | W3C  and WAI-ARIA Overview | Web Accessibility Initiative (WAI) | W3C  

Surveyor

Not having a scroll bar to keep the tools needed available while typing requires scrolling up and down the page to add anything other than text.  When creating a list of internet resources on a page, one must create several links, for each, the link title would be typed and highlighted, then scroll up to the top of the page to create the link, then back down to add the next item.  Keeping the toolbar at the top of the page by allowing scrolling of text would reduce the wasted time when using any tool on any extended page/text field.  Please correct this oversight.

Community Member

"Working as designed".  Ha!  That one is getting old. 

The new RCE isn't very functional.  Period.  Faculty get used to how you do something and they don't like change like this.  We will be the ones who hear it.  I can't imagine that the whole of Instructure isn't reeling with all of this talk of selling to Coma Bravo, but I hope there are still a few that care about their users experience. 

Surveyor

Ultimately the problem that I have with the editor is that some of the functionality of the OLD editor was lost with this new one.  To be more specific, I used to be able to create a link in a Page, then upload a file to my choice of folder to quickly give student's access to just-in-time material.  Now, in order to maintain my folder organization, I must first upload the file and then separately create the link in a Page.  As a result, it creates more work for me as faculty to keep my student's just-in-time resources updated and my course organized for easy reference.

Surveyor II

You're right, Kissler; the new system--which just got dropped on us randomly in the middle of the freakin' semester with no way to return to the old one!--has different/missing functionality, and this is not cool at all.  I've wasted so much time trying to figure out what all the icons mean and whether or not I can still do what I need to do.  We instructors need the mandatory interfaces we have to deal with to be easy to use and intuitive, and we should have the option to turn certain features on or off according to our individual course needs.

Explorer III

Could you request to have the ability to turn the new RCE on and off within the course at the Instructor's discretion? That's what they did on my campus and I am very thank ful for it.

Good luck, I feel your pain!

Learner II

Not only the top toolbar has to be static, the bottom toolbar needs to be static too.

Some of us work directly with the HTML code. We do not wish to scroll all the way down to switch to code view.