Xinha Discussion Forum

I wrapped your table around the textarea in my own testbed file and it works fine.  I see you are using a slightly older version, can you try updating and give it another go please.

Also try removing the doctype and see if that makes any difference (although I tried it with your doctype as well and it worked).

See bug http://xinha.python-hosting.com/ticket/337

Two reasons..
1. sometimes fixing bugs causes, or simply exposes other bugs
2. recently some changes were introduced into the trunk without discussing them properly first, currently the only remaining bug from these is http://xinha.python-hosting.com/ticket/337 .  At this stage I am awaiting to see if somebody will fix this problem, if nobody does I might look at it to see if it's an easy fix, or will rollback the changes mentioned in http://xinha.python-hosting.com/ticket/329 I have discussed this with the developer in question and hopefully we won't see new core features introduced without discussion in future.

Errr.  If you don't want HTML, why are you using Xinha?  Xinha is an HTML editor, not a text editor.

Dortamur: I don't like those table popups either, waaay to complicated for the average joe.  Sometime in the future a simplified table operations plugin will be made.

KHTML developers recently backported some stuff such that konq can now also pass the acid-2 test for CSS. But that does not include the contenteditable stuff.  I havn't used KDE in a long time (and don't have it installed any more) so if somebody sees them come up with contenteditable be sure and post here so I know to go have a look.

Using Xinha in your production environment is perfectly safe AS LONG AS YOU TEST IT AND ARE HAPPY WITH THE VERSION YOU USE.

Don't just blindly upgrade and put it in a production system without testing, because things will break from time to time.

Interesting

Wll, it would prevent IE from eating 10 meg per page load.  But I honestly dont' know if it's remotely realistic to try and fix it, I suspect not, I don't even know where to begin.

Lets not forget that this is a bug in IE, not Xinha.  We do everything right, it's IE that leaks memory like a sieve.

Lots and lots of leaks.  Plenty in the toolbar as I thought might be the case, but also a large number elsewhere.

Not sure on this one.  As I recall it's a built in.  If it displays in the full_example with no plugins selected then it should display in your editor providing you don't modify the toolbar.

They do similar things, FormOperations uses a panel-based interface and handles less attributes of the forms & elements.

This plugin is a special one, it works in the background, and only with Gecko based browsers, it (tries to) makes the behaviour when pressing the enter key in these browsers to be "correct" (and in line with IE) in that it creates a new paragraph instead of just inserting a <br /> tag.  You don't need to explicitly load EP, you just set xinha_config.mozParaHandler to 'best'  (there is some debate as to whether it really is 'best' and you might be better to just use 'built-in' and have <br/>s instead of paragraphs).

It's open source, free both as in beer and speech, so do whatever you like to it ;-)  Linker particularly you are very likely to want to create your own backend.

Looks nice, not quite what I was looking for but I might be able to do a bit of hacking to it .  For reording Xinha toolbars though it looks like just the thing (cept we will be using it horizontally )