On 2015-01-28 3:21 PM, Boris Zbarsky wrote:
On 1/28/15 7:21 AM, Josh Matthews wrote:
My current line of thinking is that we send a message to the compositor
that puts the pipeline in the modal state and pops up a dialog.
Additionally, the message contains a Sender, with the script task
waiting synchronously on the corresponding Receiver; when the alert box
is closed, the compositor sends a value to the script task that causes
it to resume.
Does this allow the user to close or navigate the tab and have the alert
box auto-dismiss?
-Boris
Those are good points. Since those events go through the regular script
event loop, we would presumably have to process every pending script
event in line before them, which could be bad? Stuff like
>setTimeout(function() { window.location = "http://google.com";; }, 0)
>alert("hi there")
would certainly cause observable behaviour differences vs. having task
queues that can be blocked and unblocked independently.
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
