[wp-trac] [WordPress Trac] #40951: New Text Widget - Switching Between Visual/Text Editor Strips Out Code

[WordPress Trac]

#40951: New Text Widget - Switching Between Visual/Text Editor Strips Out Code
-------------------------------------------------+-------------------------
 Reporter:  dwrippe                              |       Owner:
     Type:  defect (bug)                         |  westonruter
 Priority:  normal                               |      Status:  reopened
Component:  Widgets                              |   Milestone:  4.8.1
 Severity:  major                                |     Version:  4.8
 Keywords:  needs-testing has-unit-tests has-    |  Resolution:
  patch commit fixed-major                       |     Focuses:
-------------------------------------------------+-------------------------

Comment (by westonruter):

 @FolioVision I believe the rationale for this is largely contained in
 [comment:63 my comment above]. It's the second proposal I described there:

 > Another solution proposed was to revert the Text widget back to its
 original state (maybe renaming to HTML Code widget) and introduce a new
 Rich Text widget. However, a key reason for letting the existing Text
 widget remain upgraded with TinyMCE is that novice users who previously
 have just put simple text into the widget should by default get the new
 visual editing experience. Novice users shouldn't have to be bothered with
 copy/pasting the contents of their widget into a separate widget in order
 to start doing visual editing, in the same way that they don't have to
 switch between post editing experiences.

 I think another (maybe) unspoken goal here is to kill off the “wpautop”
 checkbox. With what is now committed to `trunk`, users will still be able
 to move content from Text widgets over to Custom HTML widgets at their
 leisure, due now to the legacy mode.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/40951#comment:144>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform