Tried the suggested work around
and it worked, but only for that editing session. If I then saved th eupdated present and attempted to edit it a second time the same problem appears, only this time the only way to get it to work was to delete the div I had entered in the previous editing session and adding it again plus any editing that I want to do this time. By the way if I had added 3 divs in the first editing session then I have to delete all three in the second editing session to regain correct functionality. So basically the work around does not work or is impracticle.
I seems that you have to go back to the original template layout each time to get correct functionality. i.e.: Remove all previous editing then add it again plus any further editing. This is the only way to get it to work correctly, but as I hope that you can see, totally impractical.
Until some years ago I was also a software engineer working in assembly, C++ and Fortran. BAsed on that experience and appologizing in advance if I am way off trach here!!! Can I suggest what I can derive from what I have seen?
The first assumption I will make is that the fundemental editing functionality is working. I assume this as the first edit appears to work fine, it is only subsequent edits that experience the problem. By definition you must save your first edit before you can start a second editing session.
So the logical possabilities are:
A) The updated edit data is incorrect or currupt in some way during either its contruction or saving to fixed media.
B) The retrieval of the stored data is corrupting what was stored and the corrupted data is causing the editing functionality of the system to mis-behave.
C) The problem lies within the editing functionality of the system. 'Bubbeling events' and children not passing the correct event data on to parents to handle default handling procedures. Just a gut feeling, nothing in particular. Just reminds me of problem from my distant past!!
ANyway, hope you get it sorted soon.