Item14365: Add ability to hide / protect code sections when using WYSIWYG editor

Many people who use the WYSIWYG editor don't want to (or need to) see things such as HTML comments and wiki "code". More to the point, WYSI editing of code sections can be problematic. Variables, plugin code, div directives, HTML comments, CSS... these things are far more likely to be broken by WYSI(A)WYG editing than simple markup / content.

It would be convenient to be able to hide code directives from casual editors using the WYSIWYG editor, i.e. to let them see and edit only the textual content without ever being exposed to the back-end administrative "stuff". (If you use Raw mode editing, everything should be displayed as usual.)

Suggestion: Perhaps something like %STARTSECTION{"rawmode"}% ... %ENDSECTION {"rawmode"}% would be a good option. If we think of a topic as the "template" for the WYSI editor, there's a certain consistency to using SECTIONs.

-- VickiBrown - 01 Apr 2017

Could this be done using css for the <sticky>...</sticky> wrapper?

-- MichaelDaum - 03 Apr 2017

This seems to be a duplicate of Support.Question1868.

-- MichaelDaum - 04 Apr 2017

1868? Not in any way that is obvious.

-- VickiBrown - 04 Apr 2017

Marking this as needs proposal. It does seem to be a reasonable idea - a sectional implementation of "NOWYSIWYG", which is currently all or nothing for a topic. It might be pretty tricky to implement though, as if the hidden section has to be somehow preserved through the edit round-trip. It might be easiest done if the block were at the beginning or end of a topic. But if it required a "Place-holder" in the edited text, deleting that place-holder would leave core with no idea on where to reinsert the redacted block.

So this needs a feature proposal to work out how the mechanism would work, and it needs a developer to dive into the complexities of WysiwgyPlugin.

-- GeorgeClark - 03 Jun 2017

Commenting is disabled while not logged in