Going back on new tab - close tab.

[mikepictor]

This is a very simple idea which I got VERY accustomed to in Arc, and makes a lot of sense to me.

If a tab is opened from another tab, and if that new tab currently has a history stack of 0 (IE you can't go "back" any further), then just close the tab on a back action. Semantically, the "previous" location is the tab that opened this one.

[rolandcrosby]

Yes please! So glad you brought this up, I'm trying out Zen now that Arc has stagnated and I didn't realize how much I expect this behavior now.

[LunarEclipse1185]

This is very much needed, please consider this feature (maybe as an option) soon. Or is there a mod for this? I'm new to Zen and Firefox and not sure if such thing is achievable.

[LaserKaspar]

This would be great!
Closing a tab using the back button when it has no history left would be a great improvement!

https://www.reddit.com/r/ArcBrowser/s/NaRjaWUY0s

[mikepictor]

so...still not a thing yet, huh? Arc started behaving weirdly on Youtube, so I am giving Zen a more serious crack, but I immediately ran into this again. Tried going back, and got so confused when I didn't go anywhere. I didn't even realise how many places opened new tabs, because I am used to just seeing them as one stream.

Here's hoping

[magnuslo]

I would looove this functionality!

[rolandcrosby]

This seems nontrivial to implement, but if anyone wants to pick it up, here are some notes on how Arc behaves as a reference. The behavior seems consistent with individual tabs having some persistent tab ID, plus a reference to the ID of the tab that they were opened from.

• when tab A opens tab B (either via target: _blank or explicit "open in new tab"), tab B's back button is enabled, and the Back action in tab B closes tab B and focuses tab A with whatever its current page is
• navigating within tab B and then invoking Back until tab B's back stack is empty preserves this behavior indefinitely (it's not like this just works ephemerally on newly-opened tabs)
• navigating to another page within tab A doesn't affect this behavior - it's the tab that's reactivated when "back" is invoked from tab B, not the specific page within tab A
• if tab A is closed, tab B's back button (at the root of tab B's back stack) gets disabled and has no effect
• but if tab A is then reopened, tab B's back button is reactivated and the behavior works again
• in fact, both tab A and tab B can be closed and reopened and this behavior will persist (as if the hypothesized "tab IDs" get saved and restored when tabs are closed and reopened)

[Wabuo]

I think for now as simple.
If back stack is 0 and the back command gets executed once more, close tap would be enough.

As in, it gives you the same behavior as if you would have just closed the tap in the tap bar and therefore follow the same focus rules on which tap to focus on after the current visible one got closed.

It wouldn't be perfect, but the behavior would be easy to understand and super simple to implement.

[Wabuo]

I just found a Firefox add-on that kinda provides this service.

It's not perfect, but for me, it's good enough.

https://addons.mozilla.org/en-US/firefox/addon/back-to-close-we/

[rolandcrosby]

how did you get this to work in Zen, and what behavior do you experience with it? "back" and Cmd-[ both still seem to be disabled in tabs with no back stack for me

[Wabuo]

It doesn't work great and seems to only work on some new taps created by following a link and seems to also only work on taps created after it was installed.

So first impression sadly was more promising than what it turned out to be ...