-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Darin Fisher wrote:
> It turns out that Firefox is single threaded, and the fact that you are > seeing multiple alerts is only an indication of some interesting and > unfortunate recursion happening on the UI thread. It is a bug, plain > and simple. It is violating assumptions about the run-to-completion > requirements of javascript in browsers. Does this assumption really exist? Is it carved in stone? After this little empirical experiment with the two alert boxes (and this experiment has been done by others before) no sane developer would assume *anything* about reliable single-threadedness in browsers any second longer. If existing Browsers have been executing JavaScript in different windows in a way that *exactly* feels and behaves like if different windows were different Threads for many years now, couldn't it be true that the real assumption made by javaScript Developers gained from their experience is "Be aware: Another window *may* have another JavaScript Thread, experiments with existing Browsers lead to this conclusion"? And isn't it just intuitive and absolutely natural to assume this from the very beginning on? Would it really break *any* *existing* JavaScript application that was already working on Firefox or Konqueror? If it is about bringing the web forward, why not postulate at this point: "From now on every browser window will have its own JavaScript thread."? Firefox developers are just trying to find a way how to officially introduce multithreading in JavaScript, so Javascript developers will be confronted with such concepts anyways. What kind of applications could possibly break? Most (if not all) applications currently are event driven and idle most of the time and most event handlers only manipulate things in their own window. I am sure you can count on one hand the applications that do such nasty things like manipulating the same data from event handlers in different windows *in* *a* *way* it could actually break something if it was not done in a thread safe way. - -- private communication within hostile networks: http://torchat.googlecode.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIxS1uxT6R4jlFoh0RApJYAJ4mcyNbgLJ4QH2KpUjX/unZ4BhMHACcC9S1 NZF3De9wGJeW3MB5O/HSwpo= =LH3e -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
