I have done this for years but today, I need to enhance some of that.

Basically, a form is posting into a transactional frame.

That transactional frame returns some code like this:

loTable=parent.MESSAGE.document.getElementById('LXToolbarIDTable')
loImage=parent.MESSAGE.document.getElementById('LXToolbarIDImage')
loTD=parent.MESSAGE.document.getElementById('LXToolbarIDTD')
loImage.style.opacity=1
loTD.style.opacity=1
loTD.innerHTML='Test'
loTable.onclick=function() {alert('onclick');}

So, basically, this goes like like:

1. A click is done on the form
2. The submit is forwarded to the transactional frame
3. The transactional frame answers with that javascript code
4. It resets the opacity of two elements from the form who did the post
5. It also needs to set back the onclick of an element to something

This works. I can click several times on the form to post and it works well.

However, from that form, if I have another click which submits something also to that transactional frame, this erases from memory the loTable.onclick reference.

So, it seems as because the onclick reference to an element of the form was set from another frame, if that frame changes URL after, it will erase anything it set in memory.

So, something has to be changed in loTable.onclick to achieve the same.

Any idea?