TabCloser

Hi Dashiell, sorry for the late reply on this! This could be a case of a conflicting Chrome extension—as I haven't seen this issue pop up for Zoom tabs specifically. There is currently an issue with Figma tabs though, as Figma changed their URL schema with the release of Slides. TabCloser was using "^https?://(?:www\.)?figma\.com/file/" to look for "files" only, those are now designated "design", "board", and "slides" for each service. On that note, I've been working this week on completely rewriting TabCloser, refactoring how tabs are detected and how they're closed (to be compliant with Manifest v3 changes coming to Chrome) and TabCloser is even more efficient and faster now, and all of the Figma issues are also addressed (and now supports Figma Design files, FigJam, and Slides)! The rewrite is available on GitHub as a pre-release test build and that may fix these issues you're having. If you want to dive into this issue further, please send an email to seth@tabcloser.com. I can snag a little more information on what's going on, I can even help you get the manual build installed on Chrome if you need, and make sure to address any unseen issues you're having in this next big release! Edit: The all new TabCloser 3 is officially live! Hopefully you can give this another whirl and see if your problems are solved! I'm still a little iffy about what could be going on with Zoom for you, either another extension is interfering or there could be additional URL parameters that need to be taken into account. Edit 2: v3.2.2 is published which should fix the issue you were having with Zoom! With their Workplace updates, some redirect URLs were changed—I've updated the regular expression accordingly to handle this. If you're still having trouble, just send an email to seth@tabcloser.com and I'll try to help you out the best I can.

Hi Denys! Thanks for the kind words and for the feedback! This is actually something that is being addressed in the next release, TabCloser 3! TC3 is actually a complete rewrite of how TabCloser works, making it more efficient, faster, an improved UI, and new features (custom URLs are coming!)—this also includes the removal of the new tab buffer! I'll be sure to update this response when the release is live so you can keep an eye out for the changes. I'm still in the middle of testing, but fingers crossed it's live by the end of July! If you have any questions or additional feedback, don't hesitate to reach out! Edit: The all new TabCloser 3 is live! The way tabs are detected is a bit different, so now the new tab buffer is completely gone! Hope you enjoy, and please don't hesitate to reach out to me at seth@tabcloser.com if you have any additional feedback or run into any issues!

Hi Charles! Thanks for taking the time to leave feedback about this. I would recommend disabling auto-close for Slack from the TabCloser menu for now! This was definitely an oversight, since I don't use Slack in any administrative capacity (aka, accessing the additional browser based settings menus) or the Slack app via the browser. Based on your feedback, I'll push an update to address the issue! I've combed through the web based pages of Slack more closely and I'll be adding some negative lookaheads to the regular expression that TabCloser is using for detecting Slack tabs to ignore "app", "customize", "account", and "home". Unfortunately Slack doesn't leave artifacts in the URL that we can look for to determine if a tab was redirected (some services do, like Notion). Regardless, I'll get this update tested and published today (check GitHub later for a manual release that should hopefully resolve this issue if you want to install it yourself). It may take a few days for it to be approved and updated for the Chrome Web Store. All the best, Seth Edit: A fix for this has been released on GitHub and is now pending approval in the Chrome Web Store. You can view the latest GitHub release (https://github.com/sethcottle/tabcloser/releases/tag/v2.7.5) to learn more about how this fix was handled. Thanks again Charles—I hope you can revisit TabCloser in the future and update your review accordingly. Don't hesitate to reach out in the future with any additional feedback. TabCloser was basically made out of my own needs for me, so a huge part of why I keep TabCloser free and open source is so the community can help contribute to, fix, provide feedback on, and keep a level transparency for how the extension functions as a whole since I can’t really test every edge case on my own! I'll leave another edit when the release has been approved on the Web Store! Edit! Looks like v2.7.5 is live on the Chrome Web Store (and elsewhere), with an all new regex schema for Slack! Thanks Charles!