이 부가 기능을 사용하시려면, Firefox를다운로드하세요.

로그인
추가 기능 아이콘

Duplicate Tabs Closer에 대한 리뷰

Duplicate Tabs Closer 제작자: Peuj

4.5 / 5
5
96
4
15
3
4
2
2
1
9
Peuj 님의 답글

개발자 답글

2달 전에 게시됨
New Tab pages are already protected and cannot be auto-closed by the extension. Both about:newtab (Firefox) and chrome://newtab/ (Chrome) are excluded from duplicate detection before any comparison or whitelist logic runs. The "" entry would have no effect since the whitelist only applies to regular HTTP(S) URLs.

If you are seeing new tabs being closed, it is possible you have a custom new tab extension that replaces the default page with a regular URL. In that case, adding that URL to the whitelist would work. If this is still happening with the current version of the extension, please open an issue at https://github.com/Peuj/duplicate-tabs-closer/issues with more details.
리뷰 126개
  • piecevcake 님, 3일 전
    This would be a 5 if "Compare by page title instead of or in addition to the URL" worked, but it doesn't.
    It only compares all titles and ignores the URLs. So all copilot tabs deleted even though they are different topics and urls.
    That is "Compare ONLY title".
    It should compare URL AND title, to exclude the same URL with different titles (re-named tabs), so the renamed tabs can be manually selected in a second run after bulk delete, to keep them.

    I nearly lost hundreds of renamed tabs because of misleading wording and bad code. And can't use bulk delete at all.

    Also, feature requests :)

    1. ignore query- can this exclude anything after the URL appended by & or ? (youtube list and timestamps, trackers etc) - it seems to exclude only Google search parameters which of course we do not want to ignore?

    2. Is it possible to have the full titles accessible in the list, either a horizontal scrollbar, or tooltips of title and URL like FF bookmarks toolbar, or selectable overflow text (like in windows explorer file properties path box)? Often retitled tabs are only different at the end.

    개발자 답글

    6시간 전에 게시됨
    Thanks for the feedback.

    For future requests, opening a GitHub issue (https://github.com/Peuj/duplicate-tabs-closer/issues) makes it easier to discuss and track.

    To clarify how "Compare with title" works: two tabs are duplicates if their URLs match OR their titles match. So tabs with the same title across different URLs (e.g., multiple Copilot sessions) are intentionally detected as duplicates.
    This is the expected behavior, and myself and other users rely on it.

    What you are describing is a different scenario: same URL, but one tab has been renamed.
    The next version will introduce a new "Detect duplicates by" option with three modes, including "URL match and same title" that keeps renamed tabs (same URL, different title are not considered duplicates).
  • W87.eu 님, 10일 전
    Absolutely perfect! Customizable, good-looking and works perfectly. Thank you, I really enjoy using it :-)
  • kartis56 님, 2달 전
    4.1.5に更新した所、保存したセッションを開いて、さらに同一タブを開いたときに重複を検知できなくなった。
    4.2.1 で治ってることを確認した。修正お疲れ様です

    개발자 답글

    2달 전에 게시됨
    Thank you for the report!

    I was unable to reproduce the issue on my end, but a fix for a related race condition was included in v4.2.0.
    Could you please test with v4.2.0 and let me know if the problem is resolved?

    If you can still reproduce it, it would really help to know:
    What you mean by "saved session" (Firefox built-in session restore, or a session manager extension such as Tab Session Manager?)
    Which mode you are using: auto-close or notify only
    Your Firefox version
    The exact steps to reproduce

    Also, if possible, could you open a GitHub issue? It makes it much easier to track and follow up: https://github.com/Peuj/duplicate-tabs-closer/issues

    Thanks again!
  • B Tang 님, 2달 전
    Works really well. You can configure it to ignore certain parts of the URL like after the search (?) part or hash (#) part of the URL as some sites will generate duplicate tabs with these parts different.
  • Firefox 사용자 17532799 님, 6달 전
  • Firefox 사용자 19514842 님, 10달 전
    Works so sell that,
    when I swithed to another pc, and the dup tabs won't close after pressing the shortcut key,
    it took me quite long to realize that i havent installed this extension on new pc yet.
  • たやまみ 님, 10달 전
  • gl00ten 님, 일 년 전
  • ilovemikael 님, 일 년 전
  • Korwin 님, 일 년 전
    Works great. I really like the "Filters" options - without them the extension would be pretty much useless to me.
  • Tempdirz 님, 2년 전
  • Kachajal 님, 2년 전
    Absolutely beautiful. Exactly what I wanted. Automatically closing older duplicate tabs when a new duplicate is opened should be a stock option in firefox.
  • Ole 님, 2년 전
    Simple, yet effective.
  • RazorCMV 님, 2년 전
  • Firefox 사용자 13609694 님, 2년 전
  • BlackWinny 님, 2년 전
    Excellent.

    Drawback: the add-on seems to have been abandoned 4 years ago, as seen on Github:
    https://github.com/Peuj/duplicate-tabs-closer

    But I find a bug:
    Whatever your choice in "Priority" parameter in the Options, the add-on always keeps the oldest visited tab. This parameter seems to not work at all.

    And I also have two little requests:
    - First one: it would be nice not to include the tabs "New tab" in the list.
    - And second one: it would be nice to disregard (ignore) a final "/".

    Both requests could have their checkbox in the Option page (with On by default).

    But I don't know what to think, given that the developments seem to have been abandoned 4 years ago.

    개발자 답글

    2달 전에 게시됨
    Hi,

    The extension was indeed quiet for a while, but development has resumed and v4.2.0 was just released today.

    Priority bug: You are right, this was a real bug. The "Keep newer tab" option was not working correctly due to a comparison error with uninitialized timestamps. It is fixed in v4.2.0.

    New Tab pages: These are already excluded from duplicate detection. Both about:newtab (Firefox) and chrome://newtab/ (Chrome) are treated as blank pages and ignored. They will not appear in the duplicate list.

    Trailing slash: Also already handled. URLs are normalized before comparison and trailing slashes are always stripped, so https://example.com/ and https://example.com are treated as the same URL.

    If you are still using the extension, updating to v4.2.0 should fix the priority issue.
  • Adrian 님, 2년 전
  • Firefox 사용자 16024671 님, 2년 전
    Write about my experience with this add-on? I wasted hours trying to figure out why I could have only one tab per domain. It didn't matter if the url was completely different. Utter POS because the PEUJ who designed it doesn't even know the meaning of "duplicate". IT MEANS "EXACTLY THE SAME", got that? Read again.

    개발자 답글

    2달 전에 게시됨
    What you experienced is the result of the "Ignore path part in URL (domain only)" option being enabled in your settings. When that option is on, the extension considers any two tabs on the same domain as duplicates, regardless of the path. It is off by default.

    Turning that option off in the Options page will restore the default behavior, where only tabs with identical URLs are considered duplicates.

    If you are still using the extension, v4.2.0 was just released with a number of UI improvements, including a clearer duplicate tabs list that shows which tabs will be closed.
  • Uday 님, 2년 전
    big productivity QoL for disorganized compulsive browsers (user)
  • akasico1 님, 3년 전
  • DeFEcT 님, 3년 전
  • arsxrs 님, 3년 전
  • A FF User 님, 3년 전
  • hacKim 님, 3년 전
  • Firefox 사용자 18054687 님, 3년 전