I think I have seen this and I may have a solution.
Check the last field in the browse(s) in question. It could be a string field, a button, doesn't matter.
Now check if that field is set as "Last in Cell" and/or "Last on Line."
I seem to recall seeing this behavior before and correcting it by making sure the last field in a row is set to "Last in Cell" and or "Last on Line."
The behavior kind of makes sense. When the form "closes", the browse thinks, "Hmmm, now which row was I on? Heck, I don't know because I don't know where one row starts and another row begins."
Anyway, I haven't ran into this in quite a while.