Re: Risky delay (was: Re: [Proto-Scripty] Re: Prototype / IE6 issue (bug?))
Hi, In the case of ie6, with less than 5% of all page views (and rapidly declining), it is now a footnote so why support it at all? stats here:http://mashable.com/2010/06/01/ie6-below-5-percent/ As is frequently the case, it's more complicated than that. :-) StatCounter may say less than 5% in the U.S., Europe, the UK, and such, but they still put it at 9.75% globally (and a whopping 20% in Asia). Net Applications gives us a higher global figure (which makes sense, they have more corporate customers than StatCounter and corporations are a big part of the IE6 longevity). More here: http://blog.niftysnippets.org/2010/10/ie6-undead-browser.html -- T.J. :-) On Nov 17, 2:07 pm, Phil Petree phil.pet...@gmail.com wrote: There comes a time in every products life cycle when you must choose which core products (e.g. browsers etc.) and platforms you will support. In the case of ie6, with less than 5% of all page views (and rapidly declining), it is now a footnote so why support it at all? stats here:http://mashable.com/2010/06/01/ie6-below-5-percent/ This be-all-to-all strategy simply doesn't work. You can't possibly support all versions of all browsers without causing a horrible and unpredictable experience for users. On Wed, Nov 17, 2010 at 7:40 AM, Bertilo Wennergren berti...@gmail.comwrote: On Wed, Nov 17, 2010 at 09:01, petrob petrob...@yahoo.com wrote: Why don't you put the evaluation part in a separate function within the scope of handleVehiclesClick and call it with some delay (100ms) to decide what and how many option elements to select? That is of course a common solution to such problems, and I use it myself a lot, but I always have a nagging worry in the back of my head: Is that really a clean and safe method? I pick a delay time, e.g. 100ms, out of thin air and then test if it works ... for me, in my browsers, in my computer, today, here. But will that be so for every user everywhere? Perhaps those 100ms will not be enough for someone using an old computer with MSIE6, or on a computer with lots of malware that sucks all the resources, or for someone who is compiling the Linux kernel while browsing, or... So maybe 500ms, or 1000ms, or... How do we test? How do we make sure? There must be a better way. Or not? Nothing to do with Prototype or scriptaculous, I know, but still... -- Bertilo Wennergren berti...@gmail.comhttp://bertilow.com -- You received this message because you are subscribed to the Google Groups Prototype script.aculo.us group. To post to this group, send email to prototype-scriptacul...@googlegroups.com. To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.comprototype-scriptaculou s%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en. -- You received this message because you are subscribed to the Google Groups Prototype script.aculo.us group. To post to this group, send email to prototype-scriptacul...@googlegroups.com. To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
Re: Risky delay (was: Re: [Proto-Scripty] Re: Prototype / IE6 issue (bug?))
It may be 20% but realistically, for most web sites, how many users come from those other countries? Like Martin said earlier, its rarely worth the effort to add advanced features into ie6 sessions as you risk breaking too much stuff in other, more significant browsers. I look at one of my larger sites which pulls 100,000 uniques a week and less than .5% are from anywhere outside North America or Europe (of course we block nigeria, russia, ivory coast etc.) On Thu, Nov 18, 2010 at 5:06 AM, T.J. Crowder t...@crowdersoftware.comwrote: Hi, In the case of ie6, with less than 5% of all page views (and rapidly declining), it is now a footnote so why support it at all? stats here:http://mashable.com/2010/06/01/ie6-below-5-percent/ As is frequently the case, it's more complicated than that. :-) StatCounter may say less than 5% in the U.S., Europe, the UK, and such, but they still put it at 9.75% globally (and a whopping 20% in Asia). Net Applications gives us a higher global figure (which makes sense, they have more corporate customers than StatCounter and corporations are a big part of the IE6 longevity). More here: http://blog.niftysnippets.org/2010/10/ie6-undead-browser.html -- T.J. :-) On Nov 17, 2:07 pm, Phil Petree phil.pet...@gmail.com wrote: There comes a time in every products life cycle when you must choose which core products (e.g. browsers etc.) and platforms you will support. In the case of ie6, with less than 5% of all page views (and rapidly declining), it is now a footnote so why support it at all? stats here:http://mashable.com/2010/06/01/ie6-below-5-percent/ This be-all-to-all strategy simply doesn't work. You can't possibly support all versions of all browsers without causing a horrible and unpredictable experience for users. On Wed, Nov 17, 2010 at 7:40 AM, Bertilo Wennergren berti...@gmail.com wrote: On Wed, Nov 17, 2010 at 09:01, petrob petrob...@yahoo.com wrote: Why don't you put the evaluation part in a separate function within the scope of handleVehiclesClick and call it with some delay (100ms) to decide what and how many option elements to select? That is of course a common solution to such problems, and I use it myself a lot, but I always have a nagging worry in the back of my head: Is that really a clean and safe method? I pick a delay time, e.g. 100ms, out of thin air and then test if it works ... for me, in my browsers, in my computer, today, here. But will that be so for every user everywhere? Perhaps those 100ms will not be enough for someone using an old computer with MSIE6, or on a computer with lots of malware that sucks all the resources, or for someone who is compiling the Linux kernel while browsing, or... So maybe 500ms, or 1000ms, or... How do we test? How do we make sure? There must be a better way. Or not? Nothing to do with Prototype or scriptaculous, I know, but still... -- Bertilo Wennergren berti...@gmail.comhttp://bertilow.com -- You received this message because you are subscribed to the Google Groups Prototype script.aculo.us group. To post to this group, send email to prototype-scriptacul...@googlegroups.com. To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.comprototype-scriptaculous%2bunsubscr...@googlegroups.comprototype-scriptaculou s%2bunsubscr...@googlegroups.com s%252bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en. -- You received this message because you are subscribed to the Google Groups Prototype script.aculo.us group. To post to this group, send email to prototype-scriptacul...@googlegroups.com. To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.comprototype-scriptaculous%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en. -- You received this message because you are subscribed to the Google Groups Prototype script.aculo.us group. To post to this group, send email to prototype-scriptacul...@googlegroups.com. To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
Re: Risky delay (was: Re: [Proto-Scripty] Re: Prototype / IE6 issue (bug?))
On Nov 18, 8:06 pm, T.J. Crowder t...@crowdersoftware.com wrote: On Nov 17, 2:07 pm, Phil Petree phil.pet...@gmail.com wrote: Hi, In the case of ie6, with less than 5% of all page views (and rapidly declining), it is now a footnote so why support it at all? The OP's issue has nothing to do with IE 6. The problem is using the wrong event, and probably the wrong control. Using onclick or onchange for a select element is a bad choice regardless of the browser being used. -- Rob -- You received this message because you are subscribed to the Google Groups Prototype script.aculo.us group. To post to this group, send email to prototype-scriptacul...@googlegroups.com. To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
Re: Risky delay (was: Re: [Proto-Scripty] Re: Prototype / IE6 issue (bug?))
On Thu, Nov 18, 2010 at 9:26 PM, RobG rg...@iinet.net.au wrote: Using onclick or onchange for a select element is a bad choice No, using onchange is actually the correct choice. He's using onclick on option elements instead of onchange (again, the correct event) on the select element. -- You received this message because you are subscribed to the Google Groups Prototype script.aculo.us group. To post to this group, send email to prototype-scriptacul...@googlegroups.com. To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
Re: Risky delay (was: Re: [Proto-Scripty] Re: Prototype / IE6 issue (bug?))
On Thu, Nov 18, 2010 at 9:36 PM, Ryan Gahl ryan.g...@gmail.com wrote: On Thu, Nov 18, 2010 at 9:26 PM, RobG rg...@iinet.net.au wrote: Using onclick or onchange for a select element is a bad choice No, using onchange is actually the correct choice. He's using onclick on option elements instead of onchange (again, the correct event) on the select element. But, yes, as RobG and I have both stated now... IE6 has nothing to do with this thread. Somehow it became an IE6 thread when in fact OP was just doing it wrong. -- You received this message because you are subscribed to the Google Groups Prototype script.aculo.us group. To post to this group, send email to prototype-scriptacul...@googlegroups.com. To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
