Item11497: set ending multi-line pre does not detect end of pre because it is encoded on a protected set statement

"text" goes into the pre block when using the WYSIWYG:

• line
     * Set var = value

text

This doesn't happen when the pre block only has one line, nor when the last line is not a Set statement. Putting a space before or a blank line after the closing pre tag makes no difference.

-- JayenAshar - 03 Feb 2012

This is on WysiwygPlugin 1.1.3 and whatever version is on f.o

-- JayenAshar - 04 Feb 2012

Confirmed, but I'm not sure how to fix it. The issue is that the close for the <pre> is on the "Set var=" line. During edit, the contents of * Set lines is encoded and protected. So the closing <pre> is "lost" to the editor.

-- GeorgeClark - 24 Apr 2012

Any way to make the value in a set line be context-dependent on the variable name? i.e., some of the variables can contain html and some can't, so only encode and protect parts that could be part of the value?

or flag the editing user if the result of TML2HTML is not balanced (no closing pre)?

or flag the editing user if the TML is not balanced (closing pre not detected because it is considered as part of the value)?

or flag the editing user if any value is unbalanced? I know this may occur in valid usage, so maybe just a different highlighting of the set statement in the wysiwyg editor is enough.

-- JayenAshar - 24 Apr 2012

This is a syntax error. You cannot close a pre block on a line where an variable definition is present. WysiwygPlugin is doing the right thing, AFAICT.

-- CrawfordCurrie - 15 Jun 2015

Commenting is disabled while not logged in