See
WysiwygTaskTeam
Current work
Updated 24 Dec 2009
Bugs
Editor
Caused by forced_root_block: false
There's some very subtle (and not so subtle) problems that are difficult to debug, caused by running with
forced_root_block: false. Moxiecode doesn't really support this mode and don't seem interested in fixing editor glitches that arise when using it. In a nutshell: they have coded some work-arounds for quirky editors but their work-around logic depends on the
ForcedBlocks? class being fully enabled (which
forced_root_block: false kills).
To that end:
- Tasks.Item2471 - Add WysiwygPlugin? option, classes to allow TinyMCEPlugin? to run without
forced_root_block: false
- Tasks.Item2254 - Fix to Item1798 introduces cursor problems for Moz browsers
- Tasks.Item1417 - Getting below a table in the Rich Text Editor is difficult / Disturbing cursor movements.
- Tasks.Item8274 - wysiwyg merges two consecutive lists
moxiecode needs to fix
These are bugs we need to report or improve existing reports on TMCE's sourceforge bug tracker.
- Tasks.Item5221: Wysiwyg tables, very difficult to get rid of paragraph html tags in table cell (persists without
forced_root_block: false)
- Tasks.Item1901: Fun with unordered lists (not sure if this persists without
forced_root_block: false)
- Tasks.Item1392: (IE only) Cursor jumps to beginning unintendedly in WYSIWYG-editor (persists without
forced_root_block: false)
WysiwygPlugin?
Usability issues
Editor
WysiwygPlugin?
- Tasks.Item1396: Improve formatting and conversion of links in WYSIWYG-editor
- Development.WysiwygContentPolicies: Implement some sort of
* Set WYSIWYG_POLICY = normal,stricttables pref setting instead of the current unwieldy WYSIWYGPLUGIN_STICKYBITS
Enhancements
Editor
WysiwygPlugin?
--
PaulHarvey - 05 Jan 2010