- From: Rob Ennals <rob.ennals@gmail.com>
- Date: Tue, 24 Nov 2009 17:43:25 -0800
Yeah. Such things could be confusing. Perhaps we would want to explicitly specify that global variable access does not release the storage mutex (I'm assuming there is no reason you would ever want it to do so?). More generally, the basic principle of this proposal is to specify what *doesn't* release the storage mutex, rather than specifying what *does*, since previous efforts to enumerate everything that releases the storage mutex seem to have got stuck. -Rob On Tue, Nov 24, 2009 at 5:36 PM, Boris Zbarsky <bzbarsky at mit.edu> wrote: > On 11/24/09 7:46 PM, Rob Ennals wrote: >> >> E.g., I may want to write: >> >> x = localStorage.bla >> localStorage.bla = x+1 > > If that's happening at global scope, the latter line involves global > variable access, which involves DOM operations (in particular, looking for > windows of that name), no? > > -Boris >
Received on Tuesday, 24 November 2009 17:43:25 UTC