On Thu, Aug 30, 2012 at 2:18 PM, Jonas Sicking jo...@sicking.cc wrote:
1. We make sure to set all element attributes before inserting the
element into the DOM. This to avoid sending notifications for
attribute modifications. The element is inserted with the right set of
attributes from the
On Mon, Sep 3, 2012 at 1:24 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, Aug 30, 2012 at 2:18 PM, Jonas Sicking jo...@sicking.cc wrote:
1. We make sure to set all element attributes before inserting the
element into the DOM. This to avoid sending notifications for
attribute
This can be implemented in script using mutation observers (provided the
parser-inserted elements question shakes out in the right direction,
which seems a prerequisite for any robust use of that API), right?
--
Glenn Maynard
Hi All,
I'd like to start by clearing up some confusion here. That's why I'm
responding to the first email in this thread.
We at mozilla have no interest in creating an API which runs the risk
of causing dead-locks. I would expect this to be true of other browser
vendors too, though obviously I
On Mon, Sep 3, 2012 at 4:47 PM, Glenn Maynard gl...@zewt.org wrote:
On Mon, Sep 3, 2012 at 4:32 PM, Jonas Sicking jo...@sicking.cc wrote:
It seems hard to ensure that deadlocks can't happen if we try to allow
blocking calls on generic MessagePorts, this is why we haven't been
interested in
On Mon, Sep 3, 2012 at 9:30 PM, Jonas Sicking jo...@sicking.cc wrote:
We can't generically block on children since we can't let the main
window block on a child. That would effectively permit synchronous IO
from the main thread which is not something that we want to allow.
The UI thread
