Context Navigation

Changes between Initial Version and Version 1 of Ticket #40951, comment 37

initial	v1
5	5	Additionally, based on the discussion in both #40907 and #core, it seemed like the decision to get the new Text Widget released was more important than, at a minimum, simultaneously releasing an HTML Code alternative and, at best, developing a solution that, while maybe not the absolute best user experience, at least didn't affect actual content and functionality and a root user level.
6	6
	7	The option of A) replacing the new text widget with an unsupported "classic text widget" plugin, and modifying database tables to accommodate, is terribly inconvenient, and the option of B) modifying core files is absolutely not going to happen (every developer knows NOT to go editing core files).
	8
7	9	The best course of action at this point, it would seem, would be to admit the error, convert the text editor back to the way it was, and simultaneously release the updated HTML Code widget along with a new Rich Text Editor. If that is completely impossible, at least figure out a way for the TinyMCE Text Editor to both default to the text editor AND remember the selected editor type (which I would hope would stop the system from stripping out existing content). That makes it a pain in the butt for developers to go in and convert to the new HTML Code widget, but '''at least it makes it possible.'''