An auto-saving session, after being opened, would
track tab creation/deletion/change and update itself (the
corresponding bookmark folder) accordingly. A session could be made an
auto-saving one or not in its edit menu for example.
Of course two auto-saving sessions shouldn't be opened in the same
window (or it should ask the user if the sessions should be merged
into one new auto-saving session maybe...).
[rationale] I talked about a user with a 'read it later' session
in another feature request. A 'read it later' would be a nice example
of an auto-saving session : the user can move a tab to the browser
window of the 'read it later' session / follow links to add an item,
and close a tab to remove the item when it has been read.
A 'replace session with current one' feature comes close, but it needs
to be done manually ; it's less convenient for some use cases, and
Firefox sometimes crash (before you did it manually).
But note that a 'read it later' session that grows too big, will
probably end up at some point as being switched back to a regular (non
auto-saving) one, because opening it would mean opening too many tabs
(then a merge current session feature makes sense too).
An auto-saving session, after being opened, would track tab creation/deletion/change and update itself (the corresponding bookmark folder) accordingly. A session could be made an auto-saving one or not in its edit menu for example.
Of course two auto-saving sessions shouldn't be opened in the same window (or it should ask the user if the sessions should be merged into one new auto-saving session maybe...).
[rationale] I talked about a user with a 'read it later' session in another feature request. A 'read it later' would be a nice example of an auto-saving session : the user can move a tab to the browser window of the 'read it later' session / follow links to add an item, and close a tab to remove the item when it has been read.
A 'replace session with current one' feature comes close, but it needs to be done manually ; it's less convenient for some use cases, and Firefox sometimes crash (before you did it manually).
But note that a 'read it later' session that grows too big, will probably end up at some point as being switched back to a regular (non auto-saving) one, because opening it would mean opening too many tabs (then a merge current session feature makes sense too).