W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2009

[whatwg] Application defined "locks"

From: Aaron Boodman <aa@google.com>
Date: Wed, 9 Sep 2009 22:03:55 -0700
Message-ID: <278fd46c0909092203t5059b846pf33ed4bc157b0aad@mail.gmail.com>
On Wed, Sep 9, 2009 at 9:13 PM, Darin Fisher<darin at chromium.org> wrote:
> If I call showModalDialog from within a database transaction, and then
> showModalDialog
> tries to create another database transaction, should I expect that the
> transaction
> can be started within the nested run loop of the modal dialog?

By definition, in that case, the second transaction would not start
until the dialog was closed.

> If not, then it may cause
> the app to get confused and never allow the dialog to be closed (e.g.,
> perhaps the close
> action is predicated on a database query.)

That is true, but it is an easily reproducible, deterministic
application bug. It also doesn't destabilize the environment -- by
making tabs or dialogs unclosable or whatever.

> Nested loops suck. ?showModalDialog sucks :-)

Fair enough.

- a
Received on Wednesday, 9 September 2009 22:03:55 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:52 UTC