Description of the issue: I currently use the Tab search function primarily as a way to view my recently closed tabs via the Recently Closed section. However, this function has been exhibiting unexpected behavior lately. Whenever I want to view recently closed tabs, I click on the Tab search button (pinned to toolbar), only for it to still display recently closed tabs as still open in the Open Tabs section. In scenarios where a large number of tabs have been closed recently, this may lead to the Open Tabs sections still being flooded with closed tabs and the Recently Closed section not displaying at all. However, this issue can be temporarily solved by quickly closing and reopening the Tab search function again, which works but is annoying to do every time. How can this issue be reproduced?
Enable the Tab search button in toolbar settings
Open new tabs (singular or multiple) for at least a few seconds
Close some tabs
Click the Tab search button in toolbar
Expected result: Only currently open tabs displayed in Open Tabs sections, while recently closed tabs are displayed in Recently Closed section
Brave Version( check About Brave): Brave 1.88.132 (Official Build) (64-bit)
Same problem, I have found if you open a new empty tab then open the tab search button and the recently closed tabs are not showing, close the tab search, then open another new empty tab (now you will have two new empty tabs showing), now open the tab search link again and now the previously closed tabs shou as they should.
I can see no one has replied from Brave, so I presume it may not get fixed.
Same issue here as you described. If you open and then close a tab, the tab search button still shows the open tab in the section, not the recently closed section.
also it seems its not adding bookmarks, it says its been added but when you open tab search and look its not there, tried a couple of times, it just does not work
Seconding this. It seems it’s referencing staled data, possibly because some/the main background service expected to keep track of tab state(for this feature?) does not run/update.
And just when I was starting to use this feature, too…
The current hack is hitting the button twice(thrice; open, close, open again) so that it’s forced to refresh, but this is even more cumbersome than it needs to be because(of chromium upstream?) there’s some sort of anti-stickyclick(like stickykeys) where you can’t hit it thrice in rapid succession to complete this fastest because interrupting the animation(?) will just re-close it…
Still happening. Though it is kinda funny to see batched combinations of all “audio playing“ tabs that never existed at the same time at the top of the interface.
Hello @itsme920 - I don’t seem to be able to replicate what you’re describing. Any chance you might be able to grab a screen recording of the behavior you’re seeing?
Hello, here’s a quick screen recording of the issue. However, I did notice that the bug does not consistently happen since I updated to 1.88.138 (the recording took a few tries).