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.
On 2015-01-28 2:24 AM, Boris Zbarsky wrote:
On 1/27/15 5:46 PM, Josh Matthews wrote:
We don't have the notion of a global event loop or anything. We
effectively have an event loop per script task (ie. event loop per TLD),
but no ability to spin it arbitrarily at the moment.
How do you plan to implement alert()? Do you plan to allow an alert
model like Firefox, where the alert doesn't freeze the entire UI?
Realistically, I think you actually want multiple event queues even per
script task (akin to the task queues in the HTML spec) and the ability
to selectively shut them off temporarily...
-Boris
_______________________________________________
dev-servo mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-servo
