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%
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
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
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.
--
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
IE6 is a buggy browser which takes much longer to do computation and
get the values from HTML elements etc. When you pop up an alert box
you actually break the running of the script and give IE6 a chance to
pull itself ( and the values) together. This is why it works properly
then, I think.
Why
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
I know there are exceptions to every rule... and I have been in your shoes
(supporting users on platforms that are no longer supported) and its a tough
walk.
On Wed, Nov 17, 2010 at 9:13 AM, matt.asbury matt.asb...@gmail.com wrote:
I appreciate your standpoint Phil but as web developers we
On 17 November 2010 14:43, Phil Petree phil.pet...@gmail.com wrote:
I know there are exceptions to every rule... and I have been in your shoes
(supporting users on platforms that are no longer supported) and its a tough
walk.
On Wed, Nov 17, 2010 at 9:13 AM, matt.asbury matt.asb...@gmail.com
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
Amen! Well said Richard!
On one site we did, we detected ie6 and did a redirect to ie6.domain.com
On Wed, Nov 17, 2010 at 10:02 AM, Richard Quadling rquadl...@gmail.comwrote:
On 17 November 2010 14:43, Phil Petree phil.pet...@gmail.com wrote:
I know there are exceptions to every rule...
this is not an IE6 issue. You're doing it wrong. First of all, the event to
listen for on selects is not click, but change (as in, you don't wire
listeners to the option elements).
In the onchange event for the select element, you then grab the value of the
selected item via something like:
var
On Nov 17, 2010, at 1:16 PM, Ryan Gahl wrote:
this is not an IE6 issue. You're doing it wrong. First of all, the
event to listen for on selects is not click, but change (as in,
you don't wire listeners to the option elements).
In the onchange event for the select element, you then grab
Sure... but my point was simply that dude was doing it wrong listening for
click events on option elements, which is why he's having the issue he's
having.
---
Warm Regards,
Ryan Gahl
On Wed, Nov 17, 2010 at 2:38 PM, Walter Lee Davis wa...@wdstudio.comwrote:
On Nov 17, 2010, at 1:16 PM,
14 matches
Mail list logo
