Can there be a delay before some features work correctly?

[carehart]

Folks, I installed the extension for the first time today (on MS Edge) and in using some features (related to closing tabs), things were not working as they should (at first). I started writing this issue to report those problems...then after a while (as I repeated steps to affirm them, while writing up an issue), things started working as they should.

So first, is there perhaps some period of time (perhaps while indexing is going on) that it could be that some features don't "work" as expected? I'll detail what those were in a moment. Second, if that indeed proves to be the case, is there any way for us to know when such indexing is going on, where we might want to wait until it's finished before trying some features? The search at least did work immediately.

Again, the problems I hit were related to closing tabs.

First, I used the feature to click the check mark next to one of a few found tabs, which shows the "close tabs" button at the top, implying that the tabs of those results we select would be closed if we click that. Instead, I found (the first time) that it closed ALL the found tabs--which was of course disappointing. (Thankfully, using the browser feature to re-open closed tabs via ctrl-shift-t brought them back.)

Second, while I was researching the FAQ to understand that, I found mention of your shortcut ctrl-shift-c to close the tabs of selected results. So I tried that...on the last of 3 results. But I found that when I did the search again, not only was that tab not closed, but the search result for it had moved UP your list by your ranking/numbering of them (in that case from 3 to 2). I did it again, and again it moved up to #1. What the what? :-)

So I came here to report those as issues, but again before I finished writing this, I tried them both one more time to double-check my steps, and now they worked as expected. To be clear, I'm confident that what I did the first times were in fact the "right" steps. So that's what made me wonder: could this be an index timing/race condition? Have you had anyone else report it?

If nothing else, I leave this for others to find if perhaps they experience either of these and come searching the issues (even if you may close this one as not a known problem).

BTW, I am using the current latest version of the extension (0.4.9) on MS Edge's latest current version as I write: Version 107.0.1418.52 (Official build) (64-bit). Thanks.