On 7/9/09 12:55, David-Sarah Hopwood wrote:
Mark S. Miller wrote:
On Wed, Jul 8, 2009 at 6:57 PM, felix<[email protected]> wrote:
I think this is not an async execution hazard,
Good. That's what I was worried about. Thanks.
it's just that a browser native function can decide
to call some arbitrary js function in the same runtime,
and event handlers are a special case of this.
Doesn't it mean that Domita can be reentered? Is Domita
robust against being reentered?
hm, yeah, it's a potential reentrancy hazard.
offhand, I can't think of anything in domita that
isn't reentrant, but it does need to be checked.
most of the calls to real dom functions are
effectively tail calls, eg, domita's el.foo()
does some checks, then calls el.node___.foo(),
so there's no particular problem with that.
I guess we also need to verify that browsers
will never run event handlers at arbitrary times.
my instinct is that too many things would be broken
if browsers actually did that, but I'm kind of surprised
that el.focus() can immediately call event handlers,
so dunno.
