Closed
Bug 1594214
Opened 5 years ago
Closed 4 years ago
Should be able to create a tab-modal prompter from the parent process based on a browsing context
Categories
(Toolkit Graveyard :: Notifications and Alerts, task, P3)
Toolkit Graveyard
Notifications and Alerts
Tracking
(firefox72 affected)
RESOLVED
DUPLICATE
of bug 1615588
Tracking | Status | |
---|---|---|
firefox72 | --- | affected |
People
(Reporter: Gijs, Assigned: pbz)
References
Details
Right now nsIPrompt interface methods (alert, prompt, etc.) take a mozIDOMWindowProxy to use as a parent. This means that now that we have documentchannel, when I'm in the parent process, I can't cause a tab-modal prompt for the relevant tab because I don't (and can't) have a reference to a DOM window, which is in a child process.
We should change the APIs to take a browsingcontext. This isn't super trivial because the geckoview implementation will also want to do something sensible in this case.
This will help switch prompts to be tab modal.
Updated•4 years ago
|
Priority: -- → P3
Assignee | ||
Updated•4 years ago
|
Assignee: nobody → pbz
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•4 years ago
|
||
Now that Bug 1615588 landed, prompting with BrowsingContext
is supported and the preferred way to show prompts.
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
Updated•10 months ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•