Downlevel browsers
-
Under what circumstances would someone be forced to use a pre-Gecko or pre IE4 browser? cheers, Chris Maunder
CodeProject.com : C++ MVP
-
Under what circumstances would someone be forced to use a pre-Gecko or pre IE4 browser? cheers, Chris Maunder
CodeProject.com : C++ MVP
Possibly corporate policy? Or because they're using a really old computer? Or (and this is most likely) they're using some kind of screen reading technology that just doesn't understand css/javascript/etc...
-
Under what circumstances would someone be forced to use a pre-Gecko or pre IE4 browser? cheers, Chris Maunder
CodeProject.com : C++ MVP
Does this question actually have a solution or is it one of those "trick questions"? You're testing us, aren't you Maunder?
-
Possibly corporate policy? Or because they're using a really old computer? Or (and this is most likely) they're using some kind of screen reading technology that just doesn't understand css/javascript/etc...
Do you think there could be a legitimate corporate policy for using downlevel browsers (IE3 and Netscape 4 are, like, way more secure than Firefox, we're don't want to upgrade everyone because the new menus are too scary for everyone), or just laziness? cheers, Chris Maunder
CodeProject.com : C++ MVP
-
Does this question actually have a solution or is it one of those "trick questions"? You're testing us, aren't you Maunder?
It just occurred to me as I was working on some old code covered with the layer upon layer of scars and wounds of old workarounds that, logically, there is be a point in time where support for old technology can be abandoned. Yet in web design this is sligtly tricky becuase as one set of downlevel browsers go the way of the dodo, other devices with limited browser capabilities (such as PDAs and phones) are rising up to fill the gap. As well, accessibility considerations, low bandwidth, and disabled javascript means there always has to be consideration taken for the downlevel browser. But now I'm thinking "just how 'downlevel' is the minimum standard of 'downlevel' these days?" cheers, Chris Maunder
CodeProject.com : C++ MVP
-
It just occurred to me as I was working on some old code covered with the layer upon layer of scars and wounds of old workarounds that, logically, there is be a point in time where support for old technology can be abandoned. Yet in web design this is sligtly tricky becuase as one set of downlevel browsers go the way of the dodo, other devices with limited browser capabilities (such as PDAs and phones) are rising up to fill the gap. As well, accessibility considerations, low bandwidth, and disabled javascript means there always has to be consideration taken for the downlevel browser. But now I'm thinking "just how 'downlevel' is the minimum standard of 'downlevel' these days?" cheers, Chris Maunder
CodeProject.com : C++ MVP
Can't you find some browser stats on the web? For example, I recently completed a web application that makes heavy use of JavaScript. When I embarked on the project I used JS v1.5 without realising that this won't work in IE5 or earlier. I checked browser stats available from our proxy server and didn't find a single instance of IE5 - all versions of IE were v5.5 or greater. So, after discussing it with my boss, we decided to leave the code as is, and so far, no-one has complained. :) There has to be a point when you say "enough" IMHO. It's like the Apple OSX vs. MS Windows discussion that popped up earlier this week. I'm pretty sure that users of IE5 or earlier make up less than 5% of web users - whether you think that 5% (probably less) is worth supporting is the question. Backward comaptibility is great, but there has to come a time when the effort required to support older platforms is costing too much time and money. Funnily enough I am just about to look at a problem with one of my client apps on NT4 - sigh - I wish I could mandate W2K or higher, but NT4 still seems to be used heavily with our customer base.
-
It just occurred to me as I was working on some old code covered with the layer upon layer of scars and wounds of old workarounds that, logically, there is be a point in time where support for old technology can be abandoned. Yet in web design this is sligtly tricky becuase as one set of downlevel browsers go the way of the dodo, other devices with limited browser capabilities (such as PDAs and phones) are rising up to fill the gap. As well, accessibility considerations, low bandwidth, and disabled javascript means there always has to be consideration taken for the downlevel browser. But now I'm thinking "just how 'downlevel' is the minimum standard of 'downlevel' these days?" cheers, Chris Maunder
CodeProject.com : C++ MVP
-
Do you think there could be a legitimate corporate policy for using downlevel browsers (IE3 and Netscape 4 are, like, way more secure than Firefox, we're don't want to upgrade everyone because the new menus are too scary for everyone), or just laziness? cheers, Chris Maunder
CodeProject.com : C++ MVP
Chris Maunder wrote:
Do you think there could be a legitimate corporate policy for using downlevel browsers (IE3 and Netscape 4 are, like, way more secure than Firefox, we're don't want to upgrade everyone because the new menus are too scary for everyone), or just laziness?
Software corporate policies are created because people are lazy. I lost two potential major customers (huuuge companies) on 2005 because they used Windows 9x and IE4. A few machines were allowed to run IE5, but not allowed to access the internal network, which turned them into browsing appliances only. I don't see dead pixels anymore... Yes, even I am blogging now!
-
Under what circumstances would someone be forced to use a pre-Gecko or pre IE4 browser? cheers, Chris Maunder
CodeProject.com : C++ MVP
The only other option being that some vital body parts are chopped off?
-
Under what circumstances would someone be forced to use a pre-Gecko or pre IE4 browser? cheers, Chris Maunder
CodeProject.com : C++ MVP
maybe i will reply to something else than you asked i hate space technology and bandwith wasting at web pages i see no reason for it, personaly i do not like web 2.0 mail clients, the most i hate is opening of pages via js i like my browser is web _client_, if i want program to work with web data _i_ will install it (at least add page to trusted sites)
-
It just occurred to me as I was working on some old code covered with the layer upon layer of scars and wounds of old workarounds that, logically, there is be a point in time where support for old technology can be abandoned. Yet in web design this is sligtly tricky becuase as one set of downlevel browsers go the way of the dodo, other devices with limited browser capabilities (such as PDAs and phones) are rising up to fill the gap. As well, accessibility considerations, low bandwidth, and disabled javascript means there always has to be consideration taken for the downlevel browser. But now I'm thinking "just how 'downlevel' is the minimum standard of 'downlevel' these days?" cheers, Chris Maunder
CodeProject.com : C++ MVP
If you kill off the old dead code, you'll be my hero. :)
-
Under what circumstances would someone be forced to use a pre-Gecko or pre IE4 browser? cheers, Chris Maunder
CodeProject.com : C++ MVP
-
Under what circumstances would someone be forced to use a pre-Gecko or pre IE4 browser? cheers, Chris Maunder
CodeProject.com : C++ MVP
Just use the fancy code, Maunder - your users aren't shy, if it breaks you'll find out fast enough... :rolleyes:
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
-
Under what circumstances would someone be forced to use a pre-Gecko or pre IE4 browser? cheers, Chris Maunder
CodeProject.com : C++ MVP
-
Under what circumstances would someone be forced to use a pre-Gecko or pre IE4 browser? cheers, Chris Maunder
CodeProject.com : C++ MVP
-
Chris Maunder wrote:
Under what circumstances would someone be forced to use a pre-Gecko or pre IE4 browser?
gunpoint?
-
Under what circumstances would someone be forced to use a pre-Gecko or pre IE4 browser? cheers, Chris Maunder
CodeProject.com : C++ MVP
I do a good bit of consulting with home and small business clients, and what I've found is even if the computer is older and the client doesn't really understand how to even install a newer browser, many times the browser is already upgraded to at least version 5 of IE. Most software packages out on the market, like accounting software and antivirus packages, etc, upgrade the IE as part of their installation requirements. Even if a person wanted to stay with an old browser, they'd need to make sure when they installed pre-packaged software that the IE isn't upgraded. :) Lost in the vast sea of .NET
-
Under what circumstances would someone be forced to use a pre-Gecko or pre IE4 browser? cheers, Chris Maunder
CodeProject.com : C++ MVP