Last Comment Bug 795645 - the Tab object should have a unique id
: the Tab object should have a unique id
Product: Add-on SDK
Classification: Client Software
Component: General (show other bugs)
: unspecified
: x86 Mac OS X
P2 normal (vote)
: 1.14
Assigned To: Nobody; OK to take it and work on it
Depends on: 815804
Blocks: sdk/tabs 686035
  Show dependency treegraph
Reported: 2012-09-29 15:38 PDT by Jeff Griffiths (:canuckistani) (:⚡︎)
Modified: 2013-02-17 23:10 PST (History)
4 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---


Description User image Jeff Griffiths (:canuckistani) (:⚡︎) 2012-09-29 15:38:46 PDT
Both desktop & Fennec implement a unique id per tab, exposing this via the Tab class in the high-level tabs module would be a win:

* some uses cases could be simplified if a specific tab can be uniquely identified

* chrome has it:
Comment 1 User image Jeff Griffiths (:canuckistani) (:⚡︎) 2012-09-29 15:48:08 PDT
Pull request
Comment 2 User image Jeff Griffiths (:canuckistani) (:⚡︎) 2012-12-27 13:24:22 PST
I've updated to include some basic tests.
Comment 3 User image [github robot] 2012-12-28 00:45:40 PST
Commits pushed to master at
bug 795645: expose unique tab ids to the high-level tabs module, now including minimal tests.
Merge pull request #595 from canuckistani/bug_795645

Fix Bug 795645 expose unique tab ids to the high-level tabs module r=@erikvold
Comment 4 User image muzuiget 2013-02-17 23:10:17 PST
I test the commit but there a problem: After move the tab to other browser window, the id not the same.

The Chrome document say: The ID of the tab. Tab IDs are unique within a browser session. 

I think it's better to keep it same in the same session like Chrome, not only in a window.

Note You need to log in before you can comment on or make changes to this bug.