(In reply to J. Ryan Stinnett [:jryans] from comment #5) > Comment on attachment 8578930 [details] [diff] [review] > browser-toolbox-error-message.patch > > I am okay with adding this error display, but I think we should move this to > a separate bug, because it does not solve the issue originally reported, and > your case is different anyway. Maybe this bug can depend on a bug with your > error patch, to aid debugging the original issue? I think it makes sense, > but let me know if it seems like too much bookkeeping work... > Filed 1144392 for this. > This bug is about using the normal Browser Toolbox from the menu item, but > getting the blank window. Your steps change the assumptions of the Browser > Toolbox: it stops the server when the toolbox (that was launched via its > menu item) is closed. So, the second toolbox you start for the terminal has > no server to connect to. I actually had the same problem when just closing and reopening the browser toolbox with the menu but I knew it didn't reproduce for other people. But will need to investigate this problem further when manually listening from the first process.
Bug 945663 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to J. Ryan Stinnett [:jryans] from comment #5) > Comment on attachment 8578930 [details] [diff] [review] > browser-toolbox-error-message.patch > > I am okay with adding this error display, but I think we should move this to > a separate bug, because it does not solve the issue originally reported, and > your case is different anyway. Maybe this bug can depend on a bug with your > error patch, to aid debugging the original issue? I think it makes sense, > but let me know if it seems like too much bookkeeping work... > Filed bug 1144392 for this. > This bug is about using the normal Browser Toolbox from the menu item, but > getting the blank window. Your steps change the assumptions of the Browser > Toolbox: it stops the server when the toolbox (that was launched via its > menu item) is closed. So, the second toolbox you start for the terminal has > no server to connect to. I actually had the same problem when just closing and reopening the browser toolbox with the menu but I knew it didn't reproduce for other people. But will need to investigate this problem further when manually listening from the first process.