Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Feature request: don't replace the existing tab when changing containers

See original GitHub issue

When a navigation event triggers a container change, the current tab is replaced with a new one and window.history is lost. This is kind of frustrating when I’m opening links from a search results page and I can’t go back. Is it possible to always open a new tab if the new location is assigned to a different container?

Issue Analytics

State:
Created 6 years ago
Reactions:4
Comments:7 (2 by maintainers)

Top GitHub Comments

2reactions

quietlystormingcommented, Apr 24, 2019

It seems this is happening for me now. I’m using version 3.0.1, and when I navigate to a container-defined URL, a new tab closes and replaces the current one. Using FF 66.0.3, win8.1 x64, tested with all other add-ons disabled.

Edit: Sometimes it replaces the current tab and opens a duplicate as well. I can’t seem to pin it down.

1reaction

stoicallycommented, Jan 28, 2018

Changing the container of a existing tab is not yet possible. A possible workaround might be to open a completely new tab and leave the old one open when a requests triggers a container change (multi-account containers does that too).