Item9199: Don't offer colours that have no TML representation

TinyMCEPlugin's colour dialogue offers lots of colours that end up as <font... tags. In the spirit of working towards a WYSIWYG experience that doesn't needlessly contaminate TML documents with such mess, I am removing the extra colours.

I also seem to recall some mysterious table bugs related to <font tags and tml/html conversion, but am unable to reproduce atm.

Probably related to the fact that <font is deprecated and TinyMCE development is moving towards explicitly unsupporting deprecated HTML constructs, although we do run with the legacyoutput plugin enabled to mitigate this.

-- PaulHarvey - 25 Jun 2010

Before I start, I should probably get some thoughts from the WysiwygTaskTeam, so set you all in the WaitingFor

-- PaulHarvey - 25 Jun 2010

I think this needs a feature proposal. Some ideas off the top of my head:

• A new tag that allows specification of any colour:
  • =%COLOR{red}% some text %ENDCOLOR%
  • =%COLOR{ff8833}% some text %ENDCOLOR%
  • =%COLOR{name="red" format="some text"}%
• Proper support for div's and span's with user-defined classes or CSS
• Living with the existing =<font> soup

-- MichaelTempest - 25 Jun 2010

Thanks Michael,

For 1.1 I think I will just separate the colours into two groups - standard and extended. That way, if the user cares, it should be easier to use this dialogue and avoid non-standard colours.

-- PaulHarvey - 25 Jun 2010

Grouped the colours into Standard vs Extended to make the distinction more obvious.

-- PaulHarvey - 28 Jun 2010

Commenting is disabled while not logged in