Showing messages 1 through 3 of 3.

• cool... well wait
  2006-01-31 07:13:19  tlaurenzo1 [Reply | View]
  
  
  I think that the in-house apps are probably the biggest challenge in this area. I have experienced more than my share of them that work just fine if the browser detection logic (which seems to invariably redirect to a "Download IE 4 Now" page) is circumvented or removed. In my experience, maintenance of these apps falls to a single web developer/designer who marveled in the glory of IE back in the 4.0 days and is yet to allow for anything different. In many cases as well, I have seen 3rd-party apps that should be cross-platform which were simply installed wrong and therefore rendered inoperative on non-IE browsers.
  
  Anyway, your point is taken.
• cool... well wait
  2006-02-02 01:50:49  jwenting [Reply | View]
  
  
  App I'm currently working on is IE only because it uses IE only constructs (in the form of HTCs).
  It also uses some W3 certified CSS and Javascript code that Firefox can't handle (that part I created, and ran the W3 validators against which approved of it).
  Firefox will just act like that code isn't there at all, which prevents the main menu of the application from working under Firefox...
• cool... well wait
  2006-02-02 07:28:27  tlaurenzo1 [Reply | View]
  
  
  I've had the same problems going the other way. In my experience if you develop a non-trivial app using a single browser platform, it doesn't matter how careful you are to write cross-platform code... you are going to have to tweak it when you get it to the point where you start using other platforms. All browsers have their quirks and "Brand X" only constructs.
  
  I tend to like the development tools available with Mozilla (admittedly, I don't have VS installed, so the IE equivilents are somewhat crippled for me) so I usually start there and have to tweak for IE, et al.