Getting below a table in the Rich Text Editor is difficult. You do not see the cursor blink. There are disturbing cursor movements that jump to the top of the table.
Maybe it would help to add an additional empty line in the editor, to help users to click in that area.
Martin, you have to understand that my work is simply an integration of the Tiny MCE editor in Foswiki. If you have problems when saving or loading topics (lost content, formatting etc) then that's something I may be able to help with. If you have problems with interaction during editing (cursor movement etc), with a few small exceptions these are problems that have to be reported to, and dealt with by, the Tiny MCE developers. They are likely in turn to pass the errors on to the browser manufacturers, because in all but a few cases the problem is in the browser.
I'm really not sure how to handle some of these reports; I just don't have time to pass them on to the Tiny MCE guys and follow up with them. I'm afraid I just have to mark them "No action".
Also, there is no need to mark them for my feedback. I am just one developer, who happens to have more experience than most in this area. But anyone else can pick the errors up and fix them. please just leave new errors in "New" state; I will find them.
-- CrawfordCurrie - 04 Apr 2009
I also found Tiny's behaviour user unfriendly, if the table is at the start of the text or at the end, you are stuck.
Looking at their forums did not reveal a solution, except for a "trailing" plugin.
I have made some changes to the plugin to make it work with tables - attached. This should be placed in the plugins folder of tiny.
To the defaultInit in TinyMCEPlugin.pm add trailing in the plugin list.
I think this can be safely placed in trunk, but should be tracked for the release branch. What do you suggest?
-- ArthurClemens - 23 Dec 2009
Actually, that plugin was written against a much older TinyMCE, if I understand correctly. It is not required any more unless you are running with forced_root_block: false, like we do in Foswiki.
The proper fix is to modify the behaviour of WysiwygPlugin so that we can run without forced_root_block: false, which will also fix a few other glitches, such as the cursor jumping behaviour eg. when finishing lists in Gecko browsers.
Tasks.Item2254 and Tasks.Item2471 are high priorities for me, as soon as I fix Tasks.Item2447.
-- PaulHarvey - 24 Dec 2009
Makes sense. Changed state to "confirmed"
-- CrawfordCurrie - 10 Jan 2010
Now that Item2254 is fixed, we can get below tables. But getting above is still not possible. Maybe we can emit a <p class="deleteme"> above any table if that table were going to be the very first element?
Todo: find sf.net bug(s), ping moxie devs.
-- PaulHarvey - 15 Jun 2010
<p class="deleteme"> is certainly do-able.
-- MichaelTempest - 15 Jun 2010
Fixed in 1.1. Changed WysiwygPlugin to emit a <p> above any table at the start of the document, as Paul suggested.
-- MichaelTempest - 23 Jun 2010