just for reference, the peregrine falcon observation was updated last at 2024-08-05 11:42:09.853-05:00 via an identification by you. that’s roughly an hour before you published the original post on this thread at 2024-08-05 12:42 -05:00.
an update to the observation like this followed almost immediately by a clicking of the green arrow button is the only way that i can see that it’s possible for the green arrow buttons to be involved in triggering the symptoms of the problem you’re describing.
this – and the weirdness if you go back and forth between observations using the browser back and forward buttons – would be basically the same kind of problem related to some sort of race condition. it would be the same thing described back in the day in https://forum.inaturalist.org/t/problem-with-previous-record-functionality/3938.
for what it’s worth, race condition problems often are relatively hard to correct because they can be hard to trigger and could require a complete reworking of how a particular screen works. so would suspect it’s not actually worth trying to troubleshoot / fix this particular problem, since the effects are so minor. (if it were up to me – which it’s not – i would just merge this with the previous thread and just close them both, noting the cost / benefit calculation. often it’s best to wait until you’re planning to make another major change or redesign of the screen to address the underlying problem.)
another similarly minor race condition bug in the Identify screen was noted in https://forum.inaturalist.org/t/identify-modal-sometimes-shows-information-from-previous-observation/8408/21. i just tried to reproduce the problem there, and i was able to successfully reproduce it. so it’s not fixed, but i don’t think anyone has ever complained about it since because it’s so minor.