Item9956: Wysiwyg editor breaks the sample color in WebPreferences

The <span> used to display the color sample gets confused by the TinyMCE editor.

Quick fix is to add a <sticky block for that line.

-- GeorgeClark - 04 Nov 2010

We are working towards letting TinyMCE be as strict as it wants to be with the markup. This is moxiecode's strategy for dealing with browser quirks - as I'm sure we are all aware, the number of failure modes on different browsers (and families of browser versions) is truly staggering. Ensuring proper markup helps them reduce the number of failure modes.

That said, I do recognize that wiki authors probably expect that the markup we are having trouble with here, shouldn't requier special treatment.

Moxiecode seem reluctant to fix bugs that only affect "unsupported" configurations - and the further away from the "recommended" config we stray, the more likely we are to struggle with a buggy Foswiki integration.

MichaelTempest already did good work removing our reliance on the forced_root_block : false setting; we should also work on removing our reliance on the legacyoutput plugin, which is causing a number of bugs at the moment.

So I don't think we should turn down TinyMCE's markup cleansing.

Perhaps one option is for WysiwygPlugin to "auto-sticky" stuff that uses macros inside the tag markup...

-- PaulHarvey - 04 Nov 2010

For what it's worth, the cleansing is happening on TinyMCE startup - not save. The few config options I tried to disable the cleansing behaviour, didn't help.

-- PaulHarvey - 04 Nov 2010

The sticky solution works fine. Closing this task.

-- GeorgeClark - 04 Nov 2010

Commenting is disabled while not logged in