Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #24097
| Path | csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news.etla.org!aioe.org!.POSTED!not-for-mail |
|---|---|
| From | Richard Maher <maher_rjSPAMLESS@hotmail.com> |
| Newsgroups | comp.lang.javascript, comp.lang.java.programmer |
| Subject | Re: A JavaScript setTimeout() even canNOT interrupt a currently executing setTomeout() event! |
| Date | Thu, 16 May 2013 19:14:41 +0800 |
| Organization | Aioe.org NNTP Server |
| Lines | 38 |
| Message-ID | <kn2f31$kat$1@speranza.aioe.org> (permalink) |
| References | <kn070t$dl$1@speranza.aioe.org> <kn0b3r$e5o$1@dont-email.me> |
| NNTP-Posting-Host | jOhPn0KFjrxwuMc9OPMmCw.user.speranza.aioe.org |
| Mime-Version | 1.0 |
| Content-Type | text/plain; charset=ISO-8859-1; format=flowed |
| Content-Transfer-Encoding | 7bit |
| X-Complaints-To | abuse@aioe.org |
| User-Agent | Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 |
| X-Notice | Filtered by postfilter v. 0.8.2 |
| Xref | csiph.com comp.lang.javascript:19763 comp.lang.java.programmer:24097 |
Cross-posted to 2 groups.
Show key headers only | View raw
On 5/15/2013 11:58 PM, markspace wrote: > On 5/15/2013 7:44 AM, Richard Maher wrote: >> If, like me, you hold this truth to be self-evident then please bring >> your pitch-fork to the castle door of: - > > No. You're not much fun then. So the torch is out of the question? > >> https://bugzilla.mozilla.org/show_bug.cgi?id=856969#c44 >> >> (Java/Liveconnect is the facilitator) >> >> Is it a GTK, Geko, Windows issue? > > I followed a bit from the last post you made on this issue, and I'm > pretty sure the issue is not GTK, Geko, or Windows, but in the general > vicinity of your chair. 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. I bet my right gonad that no one here can *SHOW* me otherwise! > > They're being very nice and explaining why the issue exists and cannot > be changed. Some of the nicest, high-calibre, selfless people I've met in IT! If they could just tell me why FireFox OS/X doesn't miss a beat then I'll go away a happy man. > You have to change your own code. It's the only way. > > > Looks that way. I can deal with that.
Back to comp.lang.java.programmer | 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