LibGuides, Chrome and Rich Text Editor - a rant
Posted by Lara Skelly | 25 Jan, 2010LibGuides has changed the look and layout of the Plain Text Editor button. It used to be a small little red link at the top of the Rich Text Editor box. Now Plain Text Editor is a tab alongside the Rich Text Editor. This makes great sense to me, as I often flick between the two editors.
Unfortunately it does come with its disadvantages. One still needs to save between switching editors, which can be annoying if you want to change something quickly and see the changes. However, this is no different from before.
What bugs me most is, when working in Chrome (my preferred browser), text no longer displays in the editing box. It used to be the case that the editing tool bar occasionally disappeared, but now everything is gone. Which means that I have to work in another browser whenever I want to play on my LibGuides. And there is, as yet, no help in the Springshare Lounge.
Plain Text Editor shows the html code, which allows for 'source' editing.