Port bug 1685313: Display chrome window modal dialogs from the prompt service inside windows (use prompts.windowPromptSubDialog)
Categories
(Thunderbird :: Upstream Synchronization, task)
Tracking
(Not tracked)
People
(Reporter: Paenglab, Unassigned)
References
Details
Attachments
(1 file)
10.81 KB,
patch
|
aleca
:
feedback+
|
Details | Diff | Splinter Review |
Reporter | ||
Comment 1•5 years ago
|
||
This is my try to make the modal dialogs in-window. With this we should no more have issues with dialogs that open on the wrong screen.
When I try to open the folder properties dialog it is still opened as a normal dialog.
Alex, Magnus, is this approach wrong or am I missing something? Is still code missing FX uses to open the new print dialog in-content? Maybe you can help me making this work?
Comment 2•5 years ago
|
||
Comment 3•4 years ago
|
||
Comment 4•4 years ago
|
||
Regarding the folder properties, that does seem like something which is traditionally in a dialog.
For the folder color changes, probably better to just render a folder icon inside the dialog instead so that the user can check it there. Having to check outside/behind a dialog seems a bit odd (and apparently BigSur wants to practically enforce it).
Reporter | ||
Comment 5•4 years ago
|
||
- let offset = window.windowUtils.getBoundsWithoutFlushing(
gBrowser.selectedBrowser
We don't have a gBrowser.
Replace with
document.getElementById("tabmail").selectedBrowser
to get it
working
I tried this and I see no change. It doesn't work for me. Maybe you see the Ubuntu behaviour of centring modal dialogs in the window and dimming a bit the window content?
Comment 6•4 years ago
|
||
No, I mean, it works for the alert that pops up in the background, which I suppose would be expected. This is what it looks like: https://pasteboard.co/JQ1DZug.png. Without the patch I get the normal alert() dialog
Comment 7•4 years ago
|
||
prompts.windowPromptSubDialog could (possibly) be affect something here.
Updated•4 years ago
|
Reporter | ||
Updated•2 years ago
|
Comment 8•2 years ago
|
||
Upstream bug 1685313: has been fixed.
Updated•1 years ago
|
Description
•