Page 1 of 1

Table editing support for non-Gecko browsers?

PostPosted: Sat Jul 31, 2010 4:52 pm
by quickfur
Hi all, I'm new here, so hopefully I'm not posting in the wrong place.

I love WYMeditor! I have always been a stickler for semantic markup instead of visual markup. Currently I'm working on a project where I'm using WYMeditor to edit small bits of content on a page, and while editing tables seems to work fine on Firefox, it's a pain in Opera (no buttons for adding/removing rows/columns, can't delete the table once added without going into the markup). As this project is targeted for end-users who do not want to deal with HTML code, I'd like to know what it takes to support these table editing features in Opera. (Does it work in IE? I didn't test that yet.)

While I'm no expert in Javascript programming, I have been forced to learn some very complex JS at work, so if necessary I can make changes to the WYMeditor code, if pointed in the right direction. :-) Of course, I'll contribute all changes back to the project for others' benefit.

How exactly do the current adding/deleting buttons work? Is this completely a Gecko feature, or is there some WYMeditor code that handlees it? Is it easy to add browser-specific handling to the WYMeditor code? (I.e., detect absence of buttons feature, activate code that does it manually). Thanks in advance for the info.

Re: Table editing support for non-Gecko browsers?

PostPosted: Mon Oct 25, 2010 4:07 pm
by winhamwr
The add/remove row/column stuff in firefox is a gecko-specific thing that wymeditor doesn't control (it's not in javascript). Other wysiwyg-ish editors implement table editing functionality in pure javascript.

The ticket for this enhancement is here: http://trac.wymeditor.org/trac/ticket/193

I've taken a shot at implementing it here: http://github.com/winhamwr/wymeditor/tree/table_editing
I'd welcome any contributions or feedback. I'm using http://github.com/winhamwr/wymeditor/co ... d989e9a820 in production right now, so it's stable enough for those purposes. Right now, the only issue is that colspans and rowspans don't work perfectly (but they don't crash).