Detecting Internet Explorer 6
in [JavaScript]
|
From: David Mark on 1 Nov 2009 15:42 On Nov 1, 5:49 am, VK <schools_r...(a)yahoo.com> wrote: > David Mark wrote: > > The OP wants to target 6 and > > we know that XMLHttpRequest was not introduced until 7. Combine that > > with detection of ActiveXObject, window.external, > > document.documentElement.filters, > > document.documentElement.style.filter, document.expando, etc. and you > > can be pretty sure you've got IE6 (or at least its version of MSHTML) > > Before I thought that your preferred way to change a light bulb is to > turn yourself around the lamp (your "feature detection" stuff was > rather convincing on that). You mean the "stuff" that is now pretty much pervasive? Name one "major" (or even minor) library that hasn't been influenced by My Library and associated articles. > Now I see that I was mistaken: if you are > in the misfortune to change a light bulb then you have to call someone > so to sit on his shoulders and ask him to turn around while you are > holding the bulb. You realize you are agreeing with Stockton that the JScript toFixed bug is a good inference for IE? > The correct documented and absolutely reliable way was already given > (conditional comments and/or conditional compilation). I know. I recommended the former. Nobody uses the latter. Try re- reading the thread.
From: VK on 1 Nov 2009 16:35 David Mark wrote: > You mean the "stuff" that is now pretty much pervasive? Name one > "major" (or even minor) library that hasn't been influenced by My > Library and associated articles. Never knew about My Library and about its global influence on JavaScript library development. Something important happened I guess over 6 months when I was not posting and reading c.l.j. Well, it is a huge success I guess to make it in 6 months into all established frameworks. It is especially amazing given that just 8 months ago you were making only preliminary steps by searching a really robust way to check getElementById availability. And back in 2008 you stated that "The currently popular general-purpose JavaScript-based frameworks? You can go right down the list. They are not good and don't seem to be getting any better. For most, the only way they could get better is if they disappeared." ( http://groups.google.com/group/comp.lang.javascript/msg/9a930670c1123e82 ) BTW is this My Library as at http://www.cinsoft.net/mylib.html ? In this case jQuery, MooTools and Prototype.js are very disrespectful by not mentioning you: http://docs.jquery.com/Contributors http://mootools.net/developers http://www.prototypejs.org/core I found though one David Mark in the "list of individuals who have signed Dojo CLAs": http://www.dojotoolkit.org/dojo-contributors That must be you? > You realize you are agreeing with Stockton that the JScript toFixed > bug is a good inference for IE? What a bs? I always use official documented vendor's tools first, and different bugs and hacks only as the 2nd option. Say till very recently Safari didn't have document.compatMode property yet it had two distinct rendering mode like others. So before ver.4 some trickery had to be used. > > The correct documented and absolutely reliable way was already given > > (conditional comments and/or conditional compilation). > > I know. I recommended the former. Nobody uses the latter. Try re- > reading the thread. "Nobody" who?
From: kangax on 1 Nov 2009 17:14 VK wrote: > [...] Say till very > recently Safari didn't have document.compatMode property yet it had > two distinct rendering mode like others. So before ver.4 some trickery > had to be used. Not really. Safari 3.1.2 already has it. [...] -- kangax
From: David Mark on 1 Nov 2009 17:15 On Nov 1, 4:35 pm, VK <schools_r...(a)yahoo.com> wrote: > David Mark wrote: > > You mean the "stuff" that is now pretty much pervasive? Name one > > "major" (or even minor) library that hasn't been influenced by My > > Library and associated articles. > > Never knew about My Library and about its global influence on > JavaScript library development. Well, that's not surprising as the list of things you don't know about is staggering. > Something important happened I guess > over 6 months when I was not posting and reading c.l.j. Well, it is a > huge success I guess to make it in 6 months into all established > frameworks. Try reading first. You'll need to go back a couple of years (or just read the copyright). > It is especially amazing given that just 8 months ago you > were making only preliminary steps by searching a really robust way to > check getElementById availability. Eight months ago, you say? So early Spring of this year? Doesn't sound right. > And back in 2008 you stated that > "The currently popular general-purpose JavaScript-based frameworks? > They are not good and don't seem to > be getting any better. For most, the only way they could get better > is if they disappeared." So? Seems most of them heard me. ;) > (http://groups.google.com/group/comp.lang.javascript/msg/9a930670c1123e82 > ) > > BTW is this My Library as athttp://www.cinsoft.net/mylib.html? Yes. > In this case jQuery, MooTools and Prototype.js are very disrespectful > by not mentioning you: > http://docs.jquery.com/Contributors > http://mootools.net/developers > http://www.prototypejs.org/core Aha. You are on to something. Now keep going... > > I found though one David Mark in the "list of individuals who have > signed Dojo CLAs": > http://www.dojotoolkit.org/dojo-contributors > That must be you? Spot on! > > > You realize you are agreeing with Stockton that the JScript toFixed > > bug is a good inference for IE? > > What a bs? I always use official documented vendor's tools first, and > different bugs and hacks only as the 2nd option. It was BS, wasn't it? So why did you chime in with that? > Say till very > recently Safari didn't have document.compatMode property yet it had > two distinct rendering mode like others. So before ver.4 some trickery > had to be used. You don't know what you are talkin about (as usual). We just had this discussion (for about the umpteenth time). The algorithm used in My Library, which will be ported to Dojo in the near future, is fine for Safari 2 (among virtually every other browser released this century and some from the 90's). That code hasn't changed for years. If you want to trace the lineage further, try to find Richard's examples as that's where I got my ideas. And, until recently, most of the "majors" used browser sniffing (the trickery you refer to I assume) for this and virtually everything else. See the progression now?
From: Dr J R Stockton on 1 Nov 2009 17:17
In comp.lang.javascript message <c7ebf289-542a-4c87-a323-a67f0bbf1bd0(a)m2 5g2000vbi.googlegroups.com>, Sat, 31 Oct 2009 17:36:38, David Mark <dmark.cinsoft(a)gmail.com> posted: >On Oct 31, 6:21�pm, Dr J R Stockton <reply0...(a)merlyn.demon.co.uk> >wrote: >> In comp.lang.javascript message <e4WdnckhUoAkZXbXnZ2dnUVZ8s- >> dn...(a)brightview.com>, Sat, 31 Oct 2009 08:43:31, Swifty >> <steve.j.sw...(a)gmail.com> posted: >> >> >I know that detecting the browser is frowned upon here, but I have a >> >need to identify specifically Internet Explorer 6. >> >> Testing either >> � � (0.007).toFixed(2) >> or >> � � S = "3000000000000000000000000" ; parseFloat(S+".0")/parseFloat(S) >> will identify IE : the second in at least IE 4 to IE 8, and the first in >> all versions from the introduction of toFixed to IE 8. �Use those in >> addition to conditional compilation, and you have belt-and-braces. >> >> There is, I suppose, some risk of MS correcting those bugs; but that >> will not worry you. >> > >What should worry you is other implementations with similar bugs. Who else would do that? Only the biggest American organisations can consistently sustain that level of incompetence. -- (c) John Stockton, nr London, UK. ?@merlyn.demon.co.uk Turnpike v6.05 MIME. Web <URL:http://www.merlyn.demon.co.uk/> - FAQqish topics, acronyms & links; Astro stuff via astron-1.htm, gravity0.htm ; quotings.htm, pascal.htm, etc. No Encoding. Quotes before replies. Snip well. Write clearly. Don't Mail News. |