Well you know, the script itself can fetch content via AJAX, so I'm wondering why you appear to be using a separate AJAX routine. That could be the problem.
However, especially with forms, AJAX importation that relies upon innerHTML as so many do can cause problems as well. The form code being imported must pass strict validation. Otherwise, though a browser may be able to error correct it as a stand alone page, once it gets filtered through being assigned as innerHTML, it often won't. Further, forms are evaluated by browsers more closely via the DOM level 2 model than perhaps any other element (tables would be second I think), so mucking about with a form via innerHTML, even if all of the code is valid, often will not have the expected results.
And as I said, the imported page may get cached. If I understand what you are saying this is not happening at the moment, rather the content of the division you are importing to is cached somehow by the DHTML Window code. But if you revert to using the DHTML Window script's native AJAX function to import, it may allow the browser to cache the imported page. That's a rather easy fix if it were to come down to that.
Can you provide a link to your page?
Please post a link to the page on your site that contains the problematic code so we can check it out.
And tell me exactly what to do to see the issue.
Bookmarks