Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #19765
| From | markspace <markspace@nospam.nospam> |
|---|---|
| Newsgroups | comp.lang.javascript, comp.lang.java.programmer |
| Subject | Re: A JavaScript setTimeout() even canNOT interrupt a currently executing setTomeout() event! |
| Date | 2013-05-16 07:44 -0700 |
| Organization | A noiseless patient Spider |
| Message-ID | <kn2r53$ii3$1@dont-email.me> (permalink) |
| References | <kn070t$dl$1@speranza.aioe.org> <kn0b3r$e5o$1@dont-email.me> <kn2f31$kat$1@speranza.aioe.org> |
Cross-posted to 2 groups.
On 5/16/2013 4:14 AM, Richard Maher wrote: > > Look, you're most probably correct but it's just that ALL the WebKit > browsers behave and do what they should and even *FireFox* on OS/X is > unbreakable with my example. (Regardless of setTimeout()s, > Thread.Sleep()s, and the number of JS Tester() objects. Well as explained in that CR, there probably isn't a difference in the browser. It's just due to timing or other differences in the environment. You're going to have the same problem, or a worse one, no matter what. > I bet my right gonad that no one here can *SHOW* me otherwise! You can show us yourself, you know. Firefox is open source. Get the source, locate the bug and turn in a patch. That's the right way to complain about somebody else's software. > Looks that way. I can deal with that. This at least is a good attitude. There's a fine line between perseverance and getting diagnosed with OCD. I think it might be time to cut bait on this one and live with it.
Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
A JavaScript setTimeout() even canNOT interrupt a currently executing setTomeout() event! Richard Maher <maher_rjSPAMLESS@hotmail.com> - 2013-05-15 22:44 +0800
Re: A JavaScript setTimeout() even canNOT interrupt a currently executing setTomeout() event! markspace <markspace@nospam.nospam> - 2013-05-15 08:58 -0700
Re: A JavaScript setTimeout() even canNOT interrupt a currently executing setTomeout() event! Richard Maher <maher_rjSPAMLESS@hotmail.com> - 2013-05-16 19:14 +0800
Re: A JavaScript setTimeout() even canNOT interrupt a currently executing setTomeout() event! markspace <markspace@nospam.nospam> - 2013-05-16 07:44 -0700
Re: A JavaScript setTimeout() even canNOT interrupt a currently executing setTomeout() event! "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-05-16 00:01 +0200
Re: A JavaScript setTimeout() even canNOT interrupt a currently executing setTomeout() event! Richard Maher <maher_rjSPAMLESS@hotmail.com> - 2013-05-16 19:02 +0800
csiph-web