felix8a at gmail.com
Thu Jul 5 13:02:41 PDT 2012
I'm not worried about modal dialogs like alert(), because those are
explicitly triggered by code, and it's easy to verify that you aren't
calling alert inside some critical section. The slow script dialog is a
problem because it can happen at any time, so it's difficult to defend
On Thu, Jul 5, 2012 at 12:12 PM, Oliver Hunt <oliver at apple.com> wrote:
> I recall in the past having numerous issues with modal dialogs causing
> unexpected js execution in most engines at least in some edge cases,
> showModalDialog probably also manages to do it quite effectively.
> Basically anytime the engine needs to pump the event loop without allowing
> any kind of js execution requires the engine to jump through hoops to
> prevent even handlers. I recall alert(...) with a background asynch xhr
> being able to trigger such things in the past.
> On Jul 5, 2012, at 11:46 AM, felix <felix8a at gmail.com> wrote:
> On Thu, Jul 5, 2012 at 10:50 AM, Brendan Eich <brendan at mozilla.org> wrote:
>> Jussi Kalliokoski wrote:
>>> Ok, here's the relevant blog post I mentioned writing:
>>> . You can discuss / give feedback here or on HackerNews:
>> Seems like a bug in Firefox, a violation of HTML5 even. The slow script
>> dialog should not allow an event loop to nest. Cc'ing Boris for his opinion
>> (this may be a known bug on file, my memory dims with age).
> Yes, this is a problem for Caja, and I'm still undecided how to solve it.
> The slow script dialog can fire at any time; in particular, it can fire
> when some data structure is in an inconsistent state, and then an event
> handler firing at the same time might be able to take advantage of that
> inconsistent state.
> "It's a bug in Firefox" seems like the most straightforward answer.
> es-discuss mailing list
> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss