Hi Sean,
Maybe if the browse update is occuring via ajax (without seeing your app - im guessing), the new browse is returning invalid XHMTL.
If so, you'll get exactly the behavour you are describing.
I use Chrome to inspect the ajax packet that is sent immediately after the update, to check its valid XHTML.
Regards
Bill