Comments on: Save the Developers from the Users

By: 2008 April 01 | ORACLE-BASE Blog Aggregator

2008 April 01 | ORACLE-BASE Blog Aggregator — Mon, 14 Apr 2008 20:23:40 +0000

[...] I teased yesterday, I’ve been mucking around with virtual machines to extend my ability to test Mix. Due to the [...]

By: Jake

Jake — Fri, 04 Apr 2008 15:15:17 +0000

@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.

By: Oliver

Oliver — Fri, 04 Apr 2008 14:28:10 +0000

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

By: Jake

Jake — Tue, 01 Apr 2008 14:30:37 +0000

@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.

By: Chris Neumueller

Chris Neumueller — Tue, 01 Apr 2008 11:00:45 +0000

Oops, s/Dave/Dean/

By: Chris Neumueller

Chris Neumueller — Tue, 01 Apr 2008 11:00:09 +0000

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/).

By: Jake

Jake — Mon, 31 Mar 2008 22:54:25 +0000

@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.

By: Gary

Gary — Mon, 31 Mar 2008 22:43:37 +0000

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.

By: Jake

Jake — Mon, 31 Mar 2008 22:16:17 +0000

@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.

By: Tim Hall

Tim Hall — Mon, 31 Mar 2008 21:47:42 +0000

Hi.

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

http://browsershots.org/

Cheers

Tim…