@stinkoflaziness: Could you please provide us with a sample extension, so that it would be helpful in triaging.
Thanks..!!

#1, this is a feature request, not a bug report per se. Whether it's possible technically or not, only the chromium developers of extensions API can tell. I think you can simply set the report's component to Platform>Extensions>API and status to Untriaged.

@rkalavakuntla, sure, I will post some example on github.

@woxxom Other solution would be to add an object to the tab, that could be saved for tab's lifetime and permanent between browser restarts. For example Mozilla is working on something like "SessionStore.setTabValue", that would be a nice alternative for my feature request.

Thank you for providing more feedback. Adding requester "rkalavakuntla@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

As per C#3, as its Feature Request marking it as untriaged

This is an interesting idea.  I imagine it could be useful for extensions and potentially other consumers.

Extensions just consume the tab id from our session state.  sky@ (OWNER of c/b/sessions), is there any logic for reusing tab id across session restarts?  I see a comment that says they "may be re-used across sessions", but it's not clear to me when that is guaranteed (if ever) to happen.

This is cool that someone is interested in this. I'd love to have persistent tabs Ids after browser restart for my tabs manager extension.

My extension:
https://gitlab.com/kroppy/TreeTabsNightly/blob/master/bg_ch.js
All those listeners must keep track of tabs all the time... This is the only way I found to "recognize" tabs after restart. Seriously annoying.
Persistent tabId would solve it all! Just like Firefox which have implemented SessionStore.setTabValue (see comment 3), where I can store my own identifier and even some additional data. It works great, persists after browser restarts and lives until tab is closed (removed) by the user!
Implement something... please... please... please...

Devlin, I think that comment is just wrong.

It would certainly be possible to do this, but it would be a pain. I suspect if we wanted permanence it would make more sense to move to a GUID for the tab-id.

As of 2018-06-01, after [1], tab IDs are no longer reused so it should be simple to persist and restore.

[1] https://chromium.googlesource.com/chromium/src/+/f61f4ba03f0acc1d8ff3ce91fdf1e201fc770d9b

As of 2018-06-01, after [1], tab IDs are no longer reused so it should be simple to persist and restore.

[1] https://chromium.googlesource.com/chromium/src/+/f61f4ba03f0acc1d8ff3ce91fdf1e201fc770d9b

Now that we have non-reused tab and window IDs, can we persist them so on restore they are kept identical? It will make writing certain types of extensions much easier. I have one that I haven't published because it is very very hacky in how I track which window is the same across restarts. If we properly support it, it will lead to removing a bunch of heuristic code and I would feel comfortable publishing it to the world.

From an extensions standpoint, I would very much like to, and don't think there's any particular reason we couldn't (though I don't have the bandwidth to pursue it myself right now).