Yes - using version 3.3.5 with Firefox 152.0.3 on Linux, clicking on anything other than the link-arrow now populates the input box as expected. But clicking on the link-arrow itself now shows exactly the same behaviour as the original problem (i.e. it closes the drop-down and does nothing else).
This must be because links are always activated via a click by default (and your own mouse-event handler always ignores any <a> elements). So the issue again is that the blur-handler prematurely removes the innerHTML (including the link) for any click that is slower than 200ms. If you can’t reproduce this yourself, changing the timeout to, say, 50ms should reveal the difference in behaviour.
One way to work around this might be to replace the <a> element with a <span> and open the url programmatically within your own mousedown-handler.
I think I lost track of one of your issues here sorry! I have a follow up clarification:
When you Ctrl+click, does a new browser tab open at all, or does nothing happen outside the selection?
I had this problem too. I imported my buttons from the previous version and the default set was empty. The little gray settings icon is there but it’s hard to see, so it seemed like it wasn’t working. I removed the empty default set and it uses the imported set by default.
Sorry, I haven’t been checking the forum. When I Ctrl + click in bulk mode, I get a popup view for the selected observation - just as I would normally (ie. if I click an observation when I’m not in bulk mode). It doesn’t open a new browser tab.
And BTW - this tool greatly streamlines the work I do. To the point where I can contemplate certain audit tasks that I wouldn’t have dreamed of undertaking without it (eg. going back and reviewing thousands of old observations and revising the IDs based on updated taxonomy).
I just wish one of the options for the actions was “Agree”. There are circumstances where I’d like to be able to use “Agree” in bulk mode. I understand that this could be viewed as “dangerous”, but currently, I can add a disagreeing ID in bulk mode, or I can set various data quality flags (eg. “as good as it gets”) in bulk mode, so I can’t see how agreeing with a bunch of existing IDs can be more dangerous than that.
I think I maybe just misread your initial report? What you are describing is the intended behavior for ctrl-click. The idea is that when you are in bulk select mode clicking observations to add to your selection, you might see an observation you aren’t sure about, and ctrl-click allows you to open the observation and see the full context, all photos, etc, before deciding to add or not, without having to exit bulk mode to do so. Is there a reason this is undesirable for you?
When I made my initial report, the intended functionality wasn’t working for me in Firefox. But I tried it out later, and it was working fine. I think maybe something went wonky when I transitioned from the beta version to the official release, and then it resolved itself. I posted a followup saying that it was working, and apologizing for the initial report. Maybe it got buried under all the other notifications.
What’s the possibility of having “Agree” added to the action choices? Perhaps it has already been discussed, but the threads related to this tool are very long. I read a good chunk of the original thread for the Beta version. I can’t remember if I read the reasoning for not including “Agree” in the actions. At the time, I didn’t think I would need it, but I now have a use case for it. As I said earlier, I can’t see that it’s more dangerous than the other actions I can apply in bulk mode.
Been using it for a few days, and it completely addresses the issue I had.
I tried entering the following feature request via the tool configuration, but it then asks me to log into Github.
Currently, when you click a button or use a keyboard shortcut, the button always flashes green. If there’s a complete failure, there’s a red popup error message. When the action is to add an annotation, the button flashes green even if the annotation added disagrees with the existing annotation. I’m usually not looking at the annotation tab when I’m adding these - I’m looking at the info tab because I’m adding the annotations at the same time that I’m making the ID, and adding the annotations via keyboard shortcuts. So I can’t see what annotation is already there (most of the time, there is none).
It would be helpful if there was some warning of the disagreement - in some cases, alternative action can be taken (I have observation fields that I add to override incorrect annotations). Suggestion - have the button flash yellow if there’s a disagreement - just to give the user a heads-up that the annotation they’ve applied is just a downvote of the existing annotation.