I should point out that the change which landed for this doesn't actually make dialogs application modal, as the dialog implementation is window modal at best. But we only ever display 1 script opened dialog at a time now.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1568296 Title: Make JS dialogs app modal Status in Oxide: Fix Released Status in webbrowser-app package in Ubuntu: Triaged Bug description: Chrome only supports app-modal JS dialogs, and so does Blink (window.alert blocks the calling process). Oxide pretends to support tab-modal JS dialogs by having a per-WebContents dispatch queue. However, the behaviour is quite broken: - It's really app-modal in single process because there's only a single RenderThread. - In multi-process it's not really tab-modal - it's render-process modal (ie, only a single tab in a render process can show a JS dialog). So, if 2 tabs live in separate processes then they can display JS dialogs at the same time. But if they're from the same SiteInstance and live in the same process, they can't. We should just change the dispatch of JS dialogs to be application modal instead, so it behaves consistently in all configurations. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1568296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
