Make the CKEditor available for all text fields by default
Description
incorporates
is related to
Activity
Tiffany Stull March 19, 2021 at 2:31 PM
suggested putting the change proposed here behind a property for contrib.
Tiffany Stull December 11, 2018 at 8:59 AMEdited
Yeah, a third-style editor would be a good compromise, but if there is a way to let users change the editor menu right on the page, that would be better (e.g. start with mobile view, then regardless of the screen size of your device, let you increase the number of buttons progressively within the editor menu itself if desired, only impacting the single editor instance on the page.)
Matthew Jones December 11, 2018 at 8:38 AM
Just throwing it out there but with some effort a 3rd style editor toolbar could also be created if it was desired as well. Some half-way between mobile and full. It would take some consideration for which buttons would appear but it's entirely possible based on the backend and work that has already been done.
Tiffany Stull December 11, 2018 at 8:16 AMEdited
making mobile version appear will apply it to all editors in Sakai. Also, it is missing some important buttons that instructors use in assessments. At UVA, instructors often insert images and Kaltura media into their questions or feedback text, as well as special characters. Some instructors also use the fontawesome icons as a workaround for the SAK-40527. Finally, if a weird formatting issue thanks to copying and pasting from Word or a webpage affects a question, we Support folks may need access to the Source to assist with fixing it.
I don't think it would be beneficial to bloat the mobile view by adding back in all these buttons, especially because some of them may not work at all on a mobile device.
Matthew Jones December 11, 2018 at 8:15 AM
The size of the editor is based on the width of the browser or the preference chosen by a user to force a specific size. It could be possible to have a different sized editor based on a context (like in T&Q delivery) but it still should be overridable via user preference. This might require a little feature work, someone would have to look into it.
In the various question authoring screens in Samigo, you need to enable the CKEditor for any text fields by selecting EITHER a Show Rich-Text Editor OR Show All Rich-Text Editors link - the link available differs by question type. This is counterintuitive to users -
you don't need to enable the editor elsewhere in Sakai, and the variability of the links across question types is also confusing (see ).
This is a feature request to simply display the editor automatically for all text fields available to the instructor. Reasons for this are below.
Samigo is the only place you need to manually enable the editor to use it.
The editor is required for even basic formatting, and most instructors don't know they need to enable it before authoring a question (e.g. paragraph breaks silently fail to save if you enter them in the text boxes).
CKEditor does not open by default on editing a question with rich text content.
This is a big problem for any instructors trying to use images or LaTeX in question pool questions because accessing a question within a pool causes you to edit it. The editors are not visible on accessing the question and the rich text content is garbled into HTML tags.
- Concerns have been raised regarding the inconsistency in the UI of the Show Rich-Text Editor vs. Show All Rich-Text Editors links. Although the Show All link is helpful to open all editors when authoring a multiple choice questions, it's awkwardly placed (above the question text box) if you just want to enter rich text content in a feedback box at the bottom of the screen.
There are multiple screens in instructor authoring (Working Copies, Published Copies, AND Question Pools) that include the Show Editor type links. All of these screens will need testing/verification after the change is made. Additionally, the rich text output in student delivery and feedback will need to be verified. I have created a test plan in a Google doc (it's over a hundred steps long!) linked under the Testing section for testing after CKEditors are enabled everywhere in authoring.