What is our popup story?

[larsbergstrom]

@dati91 is currently working on step #2 in http://webbluetoothcg.github.io/web-bluetooth/#requestDevice-secure-context, which can require a popup.

For now, we can clearly just assume that popups are never allowed, but I noticed that we don't currently have any issues on:

1. Implementation of https://html.spec.whatwg.org/multipage/browsers.html#allowed-to-show-a-popup
2. What should servo do for such popups?

CC @jdm @Ms2ger

[Ms2ger]

I don't understand why the bluetooth api looks at that.

As for popups themselves: can we open new tabs from within Servo yet? We'll need to figure out a design for that, but that's more constellation than script.

[paulrouget]

When that makes sense, we should delegate that to app itself, maybe via the browser api (when iframe are used):

• https://developer.mozilla.org/en-US/docs/Web/Events/mozbrowsershowmodalprompt
• https://developer.mozilla.org/en-US/docs/Web/Events/mozbrowserusernameandpasswordrequired
• https://developer.mozilla.org/en-US/docs/Web/Events/mozbrowseropentab
• https://developer.mozilla.org/en-US/docs/Web/Events/mozbrowseropenwindow

[Ms2ger]

As long as we don't end up with anything resembling the horror show that's Gecko window opening, I'm happy.

[notriddle]

Do we need to have some sort of sensible behavior if browser.html itself tries to show a modal popup?

[jdm]

Yeah, that would be the same as some random website performing the same action in non-browser.html.

[jdm]

In terms of Servo's current abilities, we have no support for multiple windows yet. IIRC miniservo-gtk supported multiple tabs by instantiating a new Constellation for each tab. CefBrowserHost::create_browser_sync seems to be the relevant code there, judging by ServoTab::init.

[paulrouget]

We gave up on browserhtml. The new approach is to let the embedder know that it needs to show a popup. See the recent alert implementation: #20707.