Its possible to select specific tabs when connecting to a remote debugger server, but the same is not possible for multiple chrome windows. Right now the topmost app-specific window is used (i.e last navigator:browser). There should be a way to either switch between windows, or select a specific chrome window to debug when connecting. This will allow me to fix the initial purpose of bug 915444 correctly. I'd love to hear how this should be solved. From the top of my head, I would consider creating a new command similar to listTabs, i.e listWindows, that would allow advertising all chrome windows. Does that sound right or is there a better way?

For future reference, Metro (bug 934744) and Thunderbird (bug 928008) contain hacks that can be removed when this is supported properly.

My plan for this has always been to wait for bug 806775, which depends on implementing a hostAnnotations property to debuggee globals. In that case all debuggee globals could be filtered by URL and for this case even by a chrome window flag. Jim, is implementing hostAnnotations still in the cards, or do you have another approach in mind for this?

I think something like hostAnnotations is still the right thing. I put some comments in bug 801084 (the hostAnnotations implementation bug) about why I stopped working on it, and some ideas for getting it going again.

The original comment really looks like a request for bug 1059308, but feel free to reopen with better bug title.