search

backdrop / backdrop-issues

Issue tracker for Backdrop core.
144 stars 40 forks source link

[UX] Text field settings: Changing from plain to filtered text for default value requires an additional save/edit #3379

Open klonos opened 6 years ago

klonos commented 6 years ago

Describe your issue or idea

I often come across this annoying WTF (this time while testing #3378), but always forget to file an issue about it...

Steps to reproduce (if reporting a bug)

  1. Edit an existing or create a new text field of type "long" or "long with summary".
  2. In the "Text processing" section, change the value to "Filtered text (user selects text format)"

Actual behavior (if reporting a bug)

...the WYSIWYG is not loaded, so you cannot set a default value. You need to save the field settings, then edit it again, then finally set the default value:

screen shot 2018-11-11 at 2 17 44 pm

screen shot 2018-11-11 at 2 17 22 pm

Expected behavior (if reporting a bug)

We should try to make things work with #states, or alternatively load via AJAX.

klonos commented 6 years ago

...a "quick 'n' dirty" solution would be to make "Filtered text" be the default instead of plain text, as in https://www.drupal.org/project/better_formats/issues/1689630. This would partially fix the UX problem in that the user can configure format and set default value in a single save. This is true only when creating new fields though; when editing existing ones, the switch between one type of text processing and the other would still need to be a double save process.

klonos commented 6 years ago

And here's another thought... how about this?:

  1. "lock" the plain_text format that comes out of the box even further, so that no editing of its settings is allowed (we currently lock only the roles that this format is available to, so that it can be used as a fallback).
  2. Make the plain_text format a selectable option when setting a default value for text fields ("long" and "long with summary").
  3. Get rid of the entire set of "Text processing" radio options.
  4. Allow a "clone" action for the plain_text format in /admin/config/content/formats, which would allow people to use it the same way that they are using it now (as a starting point to configure a "slim" text format).
jenlampton commented 5 years ago

This issue still needs more feedback, removing milestone, but adding milestone candidate tag.