Agreed. I'm not sure there is a compelling case for ensuring perfect display of the "examples" app in IE6. There's no problem creating other web2py apps that run fine in IE6 (subject to IE6's own limitations). But it is curious that it looks OK at web2py.com but not when running from source on localhost. What exactly is wrong with the layout?
Anthony On Wednesday, February 22, 2012 11:07:31 AM UTC-5, LightDot wrote: > > My post was made in the light of web2py, perhaps it was a bit too vague. > > I'm sorry if you still need to support IE6 somewhere. Truly :) Among other > things I contract for our country's government but the departments I have > to deal with have moved away from IE6 a good while ago. I can understand > the frustration, though. > > So, let me rephrase - while I can understand using IE6 in a limited > environment (preferably intranet) for some antiquated software someone once > upon a time got vendor-locked in, this IMHO hasn't got anything to do with > the default web2py Examples or even Welcome application. > > There is absolutely no reason for web2py to display glitch free on IE6 out > of the box, even more so since that would limit the experience for other > users with modern browsers. If there are environments that have IE6 as the > only world-facing browser, than my condolences go to them, but that's also > the only thing they'll get. AFAIK, web2py already provides enough tools to > make a custom IE6 compatible layout if someone needs it. > > Speaking about IE6 in general, even entities such as Google and Amazon > have dropped IE6 support back in 2010. In EU, Microsoft itself presents IE6 > users with http://www.browserchoice.eu page. Australian MS once upon a > time compared IE6 with a spoiled milk: > http://www.windows7news.com/2010/05/16/microsoft-compares-internet-explorer-6-to-spoiled-milk/and > as we speak, MS itself is counting down the day when this sw > monstrosity can be finally and officially retired by them: > http://www.ie6countdown.com/ > > I don't believe 2012 is the time we should even remotely be speaking about > web2py and IE6. If anything, we could possibly talk about IE8 and what to > do with it. I suppose IE9 is a necessary evil until Windows 8 and IE10 come > out, but IE8... I'm afraid we are facing a "www.ie8countdown.com" > situation, which might linger for a while. Hey, someone registered that > domain in March, 2011. LOL >
