In bug 1921846, we implemented the profile selector window in about:preferences as a subdialog, rather than opening a separate dialog window. This bug reconsiders opening in a separate window dialog instead.
Bug 1947638 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
In bug 1921846, we implemented the profile selector window in about:preferences as a subdialog, rather than opening a separate dialog window. This bug reconsiders opening in a separate window dialog instead. We should be able to implement this by reusing the `window.open` arguments from the `manageProfiles` method in `browser-profiles.js`, and since `about:preferences` runs in the chrome process, we'll be able to get the correct `ChromeWindow` ref using `Services.wm.getMostRecentBrowserWindow()`. We'll also want to make sure that, if there is a dialog window open already, we should switch to it instead of opening multiple dialogs. We should be able to do something like `let existingWin = Services.wm.getMostRecentWindow("about:profilemanager")` and, if existingWin isn't null, we can just `.focus()` it to bring it to the front.
In bug 1921846, we implemented the profile selector window in about:preferences as a subdialog, rather than opening a separate dialog window. This bug reconsiders opening in a separate window dialog instead.