Xinha Discussion Forum

That is exactly what you are calling.  If you don't load the Stylist plugin, then that function isn't available.

Provided Xinha is working for you it will submit as normal, as if it was a plain textarea (infact it is a plain textarea).

If you would like this included in Xinha, please create a ticket and attach your plugin (zipped) to it, and include the changes that are necessary (don't post the whole file ) to the htmlarea.js file and note the revision of htmlarea.js you made the changes against (you can find the revision in the top few lines of the file, or the About dialog in Xinha itself).

Somebody will review it as soon as we can.

You must be using an old version, this bug was fixed a week or two back.

re: source formatting.

You can use the HTMLTidy or SuperClean plugins to do this in Mozilla.

For comparison Kim, are the FCK & Tiny using any plugins (or whatever they use), or more to the point, do they have all the features taht your 8-Plugin Xinha had ?

How does Xinha compare with no plugins to a no-plugin FCK or Tiny?

I found the reason I made that change,  http://xinha.python-hosting.com/ticket/202

essentially if you clicked a button in the toolbar before focusing the editor bad things would happen.  This is the right way of fixing this, it was either just make the buttons silently not work, or make that visible by greying them out, as every other software interface does.

Nope, nobody workign on anythng like this to me knowledge.

There is a reason for the initial disabled status of the editors if you have a dig through the tickets you'll find it, I can't remember off the top of my head.  However it certainly doesn't unload and reload plugins - unless you're seeing something I'm not, in which case please submit a ticket.

Also remember: THIS IS BETA SOFTWARE - THINGS WILL BREAK, THIS IS TO BE EXPECTED !!!

Well, you're missing closing tags but I think this would do that...

Hit the unordered list button
hit enter
hit the indent-left button
hit enter
hit enter
hit the indent-right button
hit enter
unclick the unordered list button

There are two considerations:

1. The (x)html of the popups, and xinha-editor itself
2. The (x)html produced by Xinha (inside the editor)

In the first case, our objective should not be "conforming to standards 100%" it is "well formed and working" - that is, "tag soup" is fine, as long as it's well formed (tags closed, no invalid nesting, quoted attributes, lower case etc) and it works in the browsers we care about (currently Gecko and IE, later Safari (or maybe even generic KHTML if that's possible now)).  Personally, I don't give a rats if the html in the dialogs conforms to any particular standard as long as they work and are tidy - if this was a generic interface thave could be used by alternate devices or whatever then I'd be more concerned, but it's not, it's Javascript heavy, Gecko and IE only, as long as it works there, no problem.

For the (x)html coming out of Xinha, we don't have a lot of control.  Infact, we have very little control - the browser makes the HTML.  For example when the user clicks the bold button, we just tell the browser "the user said 'do bold'", it's the browser that works out what needs to be bolded, and how it should be done, we don't get to do anything about that.  In short, the (x)html coming out of Xinha is going to be well-formed, but if it's valid for any specification, not a hope.

These are the strings returned by document.compatMode

CSS1Compat is "standards compliant mode"
BackCompat is "quirks mode"

for both browsers.