cxw42
commented
6 years ago Merge-checking needs to be coordinated with pruning. There is no reliable way to tell (as far as I know) whether a newly-created window was a Ctrl+N, a "Restore session," or some other type of window creation.
A challenging case: close a saved window, then hit Ctl+N. The new window has the same tabs as the saved window, so gets merged. Probably not what the user wanted.
Possibilities:
- prohibit merging with the most-recently-closed window (probably the easiest) (Edit Implemented in f6a3550984c568275debf7eaf892b834e0227f15)
- prompt for whether to merge (blech)
- trigger the merge check only after a chrome.windows.get(populate) call, and take different action depending on whether the number of tabs reported in the chrome.windows.create callback matches the number returned by chrome.windows.get.
- trigger pruning only after a merge-check of the number of children in the tree, ignoring possible extra tabs.
Sometimes, when you create a new window (Ctl+N), Chrome reopens the tabs you had open previously. The problem comes and goes --- see, e.g., this thread from 2017--2018, and a bug report I submitted. TabFern could have an option to kill tabs that open, e.g., within 0.5 sec. of opening a new window, which would be one workaround. Is that a feature of interest? (PS- my recent workaround is to use Vivaldi instead ;) - see #123.)
It just started happening to me for the first time in a long time after the update to Chrome 68.0.3440.106 (Official Build) (64-bit) (cohort: 68_106_win).
Edit It became a feature of interest to me, so I started working on it :D .