Boris Zbarsky fee88c0518 Bug 1167575. Ensure that we don't exit modal state while we're still waiting on a Gecko runnable in the event-loop-spinning code in nsPrompter.js. r=dolske ... If we synchronously shut down the prompt, that will exit modal state while we're still processing our mouse or key event, which happens _before_ Gecko runnable processing. Exiting modal state will generally post a runnable to run timeouts, so we can end up processing that runnable before we return from processNextEvent and unwind to whatever code did the alert() call on the web page. The upshot is that the webpage will see timeouts fire before the alert() call returns. If we exit modal state off a Gecko runnable instead, that will ensure that we return to the nsPrompter code immediately after exiting modal state, see that the prompt is no longer active, and return to the calling web page code _before_ processing any more runnables.		2016-09-01 21:31:22 -04:00
..
commonDialog.css	Bug 1141895 part 2 - Use unprefixed unicode-bidi values in internal code. r=jfkthame	2016-06-30 16:25:31 +10:00
commonDialog.js	Bug 1230462 - Change the authentiation dialog message. r=mayhemer,dolske,margaret,tanvi	2016-06-06 01:06:00 +02:00
commonDialog.xul
selectDialog.js
selectDialog.xul
tabprompts.css	Bug 622939 - Clicking anywhere on a tab-modal prompt should focus it. r=Gijs	2016-07-14 14:24:24 -04:00
tabprompts.xml	Bug 1167575. Ensure that we don't exit modal state while we're still waiting on a Gecko runnable in the event-loop-spinning code in nsPrompter.js. r=dolske	2016-09-01 21:31:22 -04:00