评分 4.4 / 5
4.4 / 5 星
- 来自 Firefox 用户 11601056，1 年前评分 5 / 5作者大哥，可以给我以前的版本档案的下载连结吗?我需要以前右边有显示日期时间的版本。感谢。。。後續：多謝解答，本來以為都還是沒法改版本，後來看清楚了要(先删除火狐现有的本插件)，刪除後那些不能按下載的按鈕就出現了，也給其他使用者參考一下，多謝。p.s.還要改手動更新才行在历史版本页应该可以下载2.2版：https://addons.mozilla.org/en-US/firefox/addon/history-in-threads/versions/ （先删除火狐现有的本插件）。如仍有问题请到github提issue：https://github.com/program-in-chinese/HistoryInThreads_WebExtension。多谢支持。
- 来自 Firefox 用户 12552268，3 年前评分 5 / 5Hello, thanks to your great work! And could there be an option so that I can view without the website icons on the left? bc some of the icons not zoomed to fit in lines are really messing it up. Better if this bug's fixed :)
开发者回应发布于 3 年前Hi, thanks for the feedback. Actually in version 2.x, the website icons are gone completely, because the APIs I used to retrieve website icons was deprecated and the replacement API isn't in place yet. Details please see: https://discourse.mozilla.org/t/api-in-webextension-to-get-icon-of-the-url-in-a-history-visit/18679
- 来自 Firefox 用户 12545700，3 年前评分 5 / 5The addon stopped working after the webextension update. I could access the page before with chrome://history_in_threads/content/historyinthreads.xul but I can't even access it from anywhere again even from the sidebar
- 来自 sputnik1，3 年前评分 5 / 5This has been one of my favorite apps for years. It's quite useful.
When I found a problem that prevented downloading of the latest version, the developer fixed it within an hour. Amazing responsiveness from a freeware developer. Thanks.
- 来自 Nestea_Zen，4 年前评分 5 / 5I cannot believe this addon exists. I found it by accident looking for a way to delete a tab's history. He even bothered with a version for pre-Australis ppl. As soon as I'll have some spare cash, I'm donating. tyvm. go chinese ppl !! ^^ :)
My seven year long history finally makes sense.Thanks a lot for the review. In the beginning I actually naively imagined that the addon would replace the built-in history function soon lol. Please help me selling it to other firefox users you know :)
- 来自 Firefox 用户 12109512，5 年前评分 4 / 51) better integrate "Clear History by Threads" into one addon
2) better support user-defined time range, e.g. 3 days1) actually it was intended to make the browsing history read-only to this addon, to simplify the addon. So I chose to separate the other features that change browsing history to other addons.
2) I can totally see the requirements there, but currently I don't see an elegant and simple way to fulfill it. If you happen to have good ideas or even can contribute to the code, you are more than welcome to contact via the repository of the project https://github.com/nobodxbodon/HistoryInThreads
- 来自 HansensDisease，5 年前评分 5 / 5Except for one very minor issue this is waaay better than the built-in history.
When I close a tab, sometimes I really just wanted to go back a few pages in the stack. History In Threads makes it simple to find -any- of the pages I clicked recently. This also works the next time I open Firefox. Undoing a closed tab won't help me in that case.
The issue I mentioned only happens if you are using another extension to manage the sidebar. This is because they don't provide an standard way to handle user-defined sidebar content.
In my case I found a kludge to get History In Threads to work better with OmniSidebar. It may also work for the other sidebar add-ons but I haven't tried it.
First create a bookmark to the chrome://history_in_threads/content/historyinthreads.xul page (mine's on the bookmark bar). Then edit it to open in the sidebar.
You'll need to enable the 'Keep the panel loaded when the sidebar closes' option in OmniSidebar. This allows its autohide feature to work with HIT.
It's not a perfect solution: if you switch away from HIT to use another sidebar you'll need to click the bookmark again to get back to HIT.
For me, History In Threads is well worth the extra effort it took to get around the limitations of those other add-ons.
开发者回应发布于 5 年前I forwarded your feedback about the incompatibility issue to the developer of OmniSidebar:
Thankfully a fix is already submitted to the code base. Hopefully this fix will be in the update of OmniSidebar soon.