The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.I really need four input filter/editor combinations:
1. Plain text which has break, url and mailto conversions enabled.
2. Plain text
3. Rich text which is TinyMCE and;
4. Rich text TinyMCE with no spell check - for IE6
Since the input format selects the editor, enable/disable rich text is deprecated. It doesn't provide auto-format (option 1).
While it is all perfectly clear to me, the combination of input filter and rich text selection is impossible to explain to users. Moreover, everything is in the wrong place - below the post. Furthermore, the input filters are collapsed. To get the right combination requires two selections (enable/disable and input type).
A simple alternative:
Create a drop-down selector above the post that presents the input filters available to the user. In my case, this would present:
Plain text
Auto-format
WYSIWYG - All Browsers except Ie6
WYSIWYG for IE6
Since each input type has an editor associated with it, this eliminates the combination of input filter and enable/disable rich text and is much clearer to the user.
Comments
Comment #1
sunFirst of all: Thanks for taking the time outline this usability issue. I was not aware, I mean, sure, I was aware that it works, but I was not aware that it already works so good that people start thinking about fundamental usability issues. :)
I can see your point. However, this needs to be considered thoroughly. Mockups would not hurt either. There are many questions involved, such as: What happens with the regular input format selector? ...and so on.
Anything in this issue should take recent changes in Drupal 7 into account: #304330: Text format widget
Comment #2
sunBetter title.
Note that your 4th format and wysiwyg profile should not be required at all, because TinyMCE's spell-checker already tests whether the current browser is IE. If the spell-checker has a bug with IE6, then you should file an issue in TinyMCE's bugtracker.
Also note that you still need the enable/disable editor toggle, because you might need to alter the content without the editor. The current toggle link "remembers" the last state for each editor on the same page, so if you disable an editor and switch to another format and back, the editor is still disabled. Additionally, we are already working on #322433: Replace default editor status option(s) with intelligent logic to really make the toggle "remember" the preferred state of a user.
Comment #3
sunTagging.
Comment #4
sunThanks for taking the time to report this issue.
However, marking as duplicate of #748980: Allow multiple editor profiles for the same format. You can follow up on that issue to track its status instead. If any information from this issue is missing in the other issue, please make sure you provide it over there.