Changes doesn't take effect without click on HTML-source-MODE

[rethus]

If i work with xinha in WYSIWYG-Mode, i had to change in HTML-SourceCode?-Mode (and back), before i save the changes. Otherwise my changes didn't take any efects.

[rethus]

I forgot: My Browser is Firefox 1.04

[niko]

could you post your setup?

or, best would be a testcase of your xinha-installation running on your website.

does IE work?

[mharrisonline]

I had exactly this problem until I did this workaround:

function getnewHTML() {
  var html = "1";
  if (html) {
    form1.text_box.value = editor.getHTML();
  }
}

<a href='' onClick=" getnewHTML();document.form1.in_action.value='Save';document.form1.submit(); return false;">Save button image goes here</a>

I'm using the old demo.html way of putting Xinha on the page, unchanged from when I used HTMLArea 3 so I don't lose the functionality of the buttons below the editor. For some reason, when I was using HTMLArea 3, I found that I could only get the updated value if I used an alert, an if statement, etc. It's pretty ugly, but it worked great after I had been frustrated for days trying to find a way to get the changes without viewing source. Weird, huh? I thought I was the only person that would ever see this problem.

[niko]

that really looks strange :D

  var html = "1";
  if (html) {

the normal solution for your problem would be to call onsubmit:

document.form1.in_action.value='Save';
document.form1.onsubmit(); //<<insert this function-call and it will work :D
document.form1.submit();
return false;

...this is because xinha copies the html-code into the textarea in the onsubmit-event. and this event is only called when a submit-button in the form is pressed, and NOT wen the .submit()-function is called! (yes, that IS strange, but the browsers behave like that :D)

[niko]

@rethus: i think this is your problem too!

[ianb@…]

I encountered this problem too (same resolution -- call form.onsumit() before form.submit()). Basically his workaround is doing almost exactly what Xinha does during onsubmit.

Should there be a "gotchas" page in the Wiki somewhere? (Or Debugging FAQ or something.) I don't see a good way to catch this particular case and warn the developer.

[mharrisonline]

After days of it not working, (and only seeing it work when submit made an alert in the demo) I was all to happy follow the rule of "If it works, don't, er, mess with it."

I'm glad to finally know now how it is really supposed to work...

[niko]

added it to FrequentlyAskedQuestions

[anonymous]

maine name is aljek