Nagios Support Forum

Hi All,

As much as we hate it IE is still used by users unfortuantely the compatibility with XI is a bit of night mare : On logging in all the widgets are in loading state:

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; InfoPath.3)
Timestamp: Tue, 5 Jul 2011 19:18:22 UTC


Message: 'id' is null or not an object
Line: 4020
Char: 5
Code: 0
URI: http://karma.khipu-networks.com/nagiosx ... /js/jit.js

I see this is an issue with the hypermap component and removing it does eventually loads the page up but at the bottom the page is throwing loads of errors where as it works a charm in FF and Chrome
I am raising this only to tell my boss why !!

Cheers
Arnab

We are looking into this and it's been added to our bug tracker: http://tracker.nagios.com/view.php?id=175

IE is about 5 years behind in adopting current web standards, which on a grand scale is really hindering the forward movement of what can be done in a web browser. The javascript visualization toolkits are able to be used because of some of the newer technologies in web development, but because of IE's lag in web standards, not everything works in it. There are 3 different javascript visualization libraries that XI uses in various components, all of the libraries themselves recommend against using with IE because of unpredictable results. The javascript toolkit for NagiosQL/Core Config Manager also has problems in IE. I think IE 9 is getting better from what I'm hearing, but we generally recommend Firefox as the most trusted browser.

Hi Mike,

We all know how much of pain IE is , none of our products even from very big vendors such as Infoblox , Cisco seem to work very well with it. Unfortunately here in the UK most of our customers are in the public sector with strict nothing else but IE policies.

Cheers
Arnab

Yeah that makes sense. I'm hoping IE 9 presents better compatibility for the visualization tools, because our dilemma isn't so much the javascript code that we've developed, but the externally developed libraries that we utilize. I will make a note to follow up on the libraries that we're using and see if they've got updates posted to improve IE compatibility.