Identify leaping from Annotations panel to Info panel

Please fill out the following sections to the best of your ability, it will help us investigate bugs if we have this information at the outset. Screenshots are especially helpful, so please provide those if you can.

Platform (Android, iOS, Website): MacOS Sequoia 15.3.1

Browser, if a website issue (Firefox, Chrome, etc) : Chrome and Safari

Description of problem (please provide a set of steps we can use to replicate the issue, and make as many as you need.):

Step 1: Add ID to any observation in Identify viewer

Step 2: Navigate (Shift+arrow key) to Annotations panel (before Info panel updates)

Step 3: Start adding Annotations (esp. with keyboard shortcuts). When Info updates the ID, the viewer automatically jumps to the Info panel, so whatever keyboard shortcuts you’re using to add annotations will screw up whatever ID you just added.

This just started happening between yesterday morning and yesterday afternoon (EST). It means having to wait until the ID updates before moving on to the Annotations panel, which doesn’t sound like a big deal…but it is a big deal when you’re trying to move quickly through hundreds of IDs. I tried it on both Chrome and Safari and the issue is identical in each browser.

4 Likes

I have also noticed this, and I don’t think I’d seen it before

3 Likes

Yep I’ve also just had this happen. Very frustrating and makes it difficult to ID in bulk quickly

5 Likes

I’ve also been getting a lot of “internal server error” popups, usually when I’ve been in another tab and then return to the tab with the Identify viewer open.

Platform: Website

Browser: Tested in Chrome and Firefox, but I assume it’s not browser specific.

Description of problem

Step 1: Open Identify dialog (to Info tab), add an ID and click “Save”

Step 2: Immediately navigate to the Annotations tab using Shift+Right, Shift+Right

Step 3a: Use a keyboard shortcut to add an Annotation (e.g. P+L to add “Flowering”)

Step 3b: At some point during this, the UI will get confirmation that the new ID from Step 1 was added and will change the focus to the Info tab. This then prevents the identifier from entering the Annotation in Step 3a as desired.

Until recently, there was no change of focus (step 3b). This allowed identifiers to efficiently process a large volume of IDs and annotations. This change makes adding IDs and annotations within the same session unproductive.

I’m guessing that this may be related to the code changes that were made for the taxon photo similarity update.

Many thanks, Rupert

5 Likes

I recently began experiencing the same issue.

2 Likes

This one is about the same issue:
https://forum.inaturalist.org/t/identify-leaping-from-annotations-panel-to-info-panel/61734

2 Likes

Added the above three posts to this topic.

2 Likes

I’m not sure if there was a code fix, but it looks like this focus grabbing behavior is not happening for me at the moment.

I’ve been taking note of when this happens, and for me it only happens when I add a new ID. It doesn’t happen when I agree with a pre-existing ID. But from my testing, the behaviour seems quite consistent - it never happens when I’m just agreeing, and it always happens when the ID I added was new.

1 Like

Yes I have noticed the same, if I agree with a pre-existing ID it does not happen, but it happens even if I manually add an ID that is just an agreement.

2 Likes

Thanks, I can replicate. I made issue here: https://github.com/inaturalist/inaturalist/issues/4415

4 Likes

I am experiencing the same bug on website (Firefox Version 135.0.1 (64-bit)). Currently adding annotations first to avoid focus grabbing.

1 Like

I seem to have found an exception to this - if I select the species from “Suggestions” I can then go to Annotations and the focus stays there - it doesn’t jump back to Info. I’ve only done this a couple of times, so I wouldn’t call it thorough testing, but thought I should make a note of it here.

This should be fixed now. Looking pretty good for me, but please test it out.

5 Likes

The problem is fixed now for me on Firefox-135.0.1.

1 Like