The following patch adds an extra property to textareas, #noMCE, that tinyMCE will obey.

This can be useful if tinyMCE makes no sense on some textareas.

For instance, webform presents select list of Options as a textarea, even though it requires a list of plain texts.

The override on the page name is not enough for this case, since there are a lot of other textareas in webform where tinyMCE is desireable.

CommentFileSizeAuthor
y.patch497 bytesespie

Comments

espie’s picture

espie commented

Post-scriptum: I since found the list of named form exceptions in the tinyMCE code, but I think that it is good to allow people to do things the other way around, namely prevent tinyMCE from taking over on specific forms.

kingandy’s picture

kingandy
he/him
commented

I think this is a beautifully elegant solution to a constant headache of mine. It's all very well overriding things at the theme level but I find myself copying-and-pasting the theme_tinymce_theme() function again and again. This would allow module developers to prevent TinyMCE from being initialised on textareas where rich text is never suitable or desirable, such as code-only areas (like the Argument Handling Code box in Views) or linebreak-dependent system fields (like the manual Related Links textbox).

In fact I think this is such a good idea that maybe it should be raised to the Forms API team? It would be great to make this into a more generic property ('#NoRich'?) that could be easily implemented by all rich text type modules.

kingandy’s picture

kingandy
he/him
commented

Ah, apparently a #wysiwyg property has already been implemented over in WYSIWYG module on the grounds of "Being Blatantly Obvious". If this gets adopted into TinyMCE at all, I'd recommend using the same property.

mupsi’s picture

mupsi
she/her
commented
Issue summary: View changes
Status: Needs review » Closed (outdated)