Support for domain-specific filters about duplicate-tabs-closer

[Peuj]

Hello,

1 - Request: configure the filters per domain
I'll provide first a simple black list.
You should be able to set something like "https://my.zammad.example/#ticket/zoom/*"
This should solve your problem.
For the filters per domain I'll see later.

2 - ...navigates the tab to the new URL (but without reloading the tab).

If I've correctly understood your idea, this is not possible.
If I change the url of the tab without loading it then you're still on the page of previous url.
So when you click on the "submit" button it will be linked the previous url not the new I've pasted.

[martinvonwittich]

2 - ...navigates the tab to the new URL (but without reloading the tab).

If I've correctly understood your idea, this is not possible.
If I change the url of the tab without loading it then you're still on the page of previous url.
So when you click on the "submit" button it will be linked the previous url not the new I've pasted.

I'll try to explain. Let's assume I currently have one ticket in Zammad opened: https://my.zammad.example/#ticket/zoom/1234

When I now paste the URL to another ticket in the address bar while I'm the Zamad tab, let's say https://my.zammad.example/#ticket/zoom/1235 , Zammad will use the hashchange event listener to catch this. Then it will load the new ticket from the server via AJAX, and refresh its view with JS to show me the new ticket. Unfortunately there doesn't seem to be a public demo to illustrate that, so I've made a short video that shows this: https://imgur.com/a/8mZH2mg

The nice thing about this is that Zammad doesn't need to completely reload here, which would take several seconds. I've made another video that illustrates a complete reload: https://imgur.com/a/4aOlSgp

So if it were possible to somehow navigate the old tab to the new URL while allowing the page to use the hashchange event listener, this would result in a noticeable speedup for users. If it's not possible, this is of course fine too; DTC (for Firefox) and Clutter Free (for Chrome) are already a significant improvement for using Zammad!

Thanks for your work!

[turing]

I second @martinvonwittich's request. This would also be fantastic for domains like facebook, where you want, effectively, a 'facebook tab' - any new URL should be routed to that tab to create the state change, and if I were to type 'facebook.com' in a new tab URL and hit enter I should simply be directed to the existing tab.

This would save me quite a lot of trouble.

[turing]

For a given blacklist item, being able to specify if the URL should be set but the page not reloaded vs. the URL set and the page reloaded would be fantastically useful

[turing]

@dnknn no, I don't. This is not about intentionally duplicating tabs with a menu item. It's about accepting text input and redirecting to a preëxisting tab.

[turing]

Any update?

[Peuj]

@turing I understand what @martinvonwittich needs and why it will work.
It would be ...the URL should be set but the page not reloaded...
I'm less sure about vs. the URL set and the page reloaded

[turing]

"any new URL should be routed to that tab to create the state change, and if I were to type 'facebook.com' in a new tab URL and hit enter I should simply be directed to the existing tab."

This is what I'm getting at.

Say I have an existing facebook tab in a window somewhere.
I open a new tab in another window and type facebook.com/
When I hit enter, I am instantly looking at the other tab instead of having made a duplicate.

Say I command click a link to a facebook URL - intending to make a new tab, instead the URL of the facebook tab is set to the target URL and the page loads.

I don't know how much flexibility you have to move tabs between windows, but all of this is about ensuring there are not numerous duplicate copies of a tab with the same domain for certain sites.