Cloning and tweaking instead of having to start from scratch is much easier for people.
This may be a step towards solving some of the UX issues discussed in #1519 too. Site admins seem to be using the "Full HTML" format as a go-to solution when content editors demand more. This is OK in general, but it creates false expectations that people will get a WYSIWYG etc.
If we provided an easy way for admins to clone the "Filtered HTML" format, then they would do that, and add buttons + allow additional HTML tags as required (which is what they should be doing).
GitHub Issue #:
4501
Recent comments
Glad it works for you! Regarding selecting options, I've just tested the Views Autocomplete Filters module and got it working after I had a look at the README and made sure to use the same...
Can't filter content in a View
You are right, that was it... Now my problem is I would like users being able to select from pre-established options, like a drop down or maybe an autocomplete. For that I would the Autocomplete...
Can't filter content in a View
Here goes the screenshot for the exposed filter config I will try the module you are telling me about. thanks again!
Can't filter content in a View