DISQUS

DISQUS Hello! Oracle AppsLab is using DISQUS, a powerful comment system, to manage its comments. Learn more.

Community Page

Jump to original thread »
Author

Save the Developers from the Users

Started by manalang · 9 months ago

TechCrunch posted a plea to Save the Developers last week imploring users to upgrade their Internet Explorer 6 browsers to Internet Explorer 7.
According to W3 Schools, more than 30% of people browsing the Interwebs use IE6, even though it is more than 6 years old. The gist of the plea is th ... Continue reading »

9 comments

  • Hi.

    You could do some of your basic testing without installign different browsers if you use this:

    http://browsershots.org/

    Cheers

    Tim...
  • @Tim: This is cool.

    Our problem is that we need to reproduce specific error conditions, usually caused by Javascript differences in IE6. A screenshot won't cut it, so we have bunches of browsers crossed with the big three O/S.
  • When you've got essential web apps that don't support IE7, you stick with IE6. Google "TestDirector IE7" for an example of the problem.
    Maybe we need a separation of rendering engine and browser UI, like the IETab extension for Firefox.
  • @Gary: I second that. IETab is a great way to do what I need, and I'd completely forgotten about it after upgrading to FF3. Good stuff.
  • Hi!

    I like your blog title ;-). Regarding JavaScript differences, there are several libraries that could help. See for example Dave Edwards' IE7-js (http://code.google.com/p/ie7-js/).
  • Oops, s/Dave/Dean/
  • @Chris: Thanks, it's a bit tongue-in-cheek. On the one hand, it would be nice to drop IE6-specific development and testing, but on the other, you can't bully your users.

    Thanks for the pointer to Dean's work.
  • several of our customers, especially the bigger cooperations, haven't upgraded to IE7 bacause
    - not all intranet apps are working well with IE7
    - the upgrade is not hasslefree
    clear profiles, reinstall certificates, ....

    If IE6 and IE7 could coexist then the switch would have been made
  • @Oliver: IE6 to IE7 shows the shift caused by Firefox; in the 5 years between the two, MSFT had to shift development to support standards and modern browser features that weren't in the original product plan for IE7.

    One bummer side effect is that apps built for IE6 never considered other browsers, and they won't port to more open browsers, including IE7. Ironic.

Add New Comment

Returning? Login