Live Map res info does not work on Internet Explorer

When you try to click a res on the map,you get a empty box,like this

Can you try to fix it?

I can try, but you should seriously consider getting Google Chrome browser

It works in google chrome? I use chromium on linux and it doesn't work at all, just get a black page, so I've had to use firefox for the live map.

Chrome FTW

The same happens to me. Empty Box=Empty void in my brain.

I mainly use Internet Explorer,but I also have Firefox.

I can take a look, but without a ton of work I don't what I will be able to do. The map is a huge program managed by an excellent team (Dynmap bukkit), they use this library for the actual mappings: http://leaflet.cloudmade.com/

Hmm just checked the leaflet site, and their home page is black, but works in firefox. It must be a problem with openSUSE's chromium build.

Or Leaflet's problem, its hard to place blame in the realm of the internet

Firefox FTW
(PS. Chrome faster.)

I just installed google's official build, and it works! I don't know why chromium didn't work, but it had been messing up with some other javascript heavy sites too, but they're working too.

i used firefox from when it was called phoenix. it used to be a nice browser up to about 3.5 after that i think they lost their way. chrome sync is the killer feature for me though. if you use several computers, its awesome.

I could not agree more, FF used to own then they lost what made them great. Chrome now owns but if history tells us anything it won't be forever.

Also Firefox take lots of time to start on older computers,it takes about 20 seconds to start Firefox on my computer.

I think FF messed up since 4 lol
3.6.3 is best for me

I've not studied the memory consumption of Firefox or Chrome, I just know before when I had 2 gb ram, opening firefox my entire computer would crawl and become pretty much unsuable. Chrome didn't do that.

Just because something forks a second process of itself, doesn't mean it's using double the ram. Modern operating systems use copy-on-write memory. So, when chrome forks a new process, it's not actually using anymore memory until the new process attempts to write to that memory (then the OS will copy that memory and mark it read-write).

I got 8gb
eat all u want
memory buffet

I assume you mean swapping to disk? If so, Firefox caused my system to swap to disk, because closing it made my computer usable again, and opening chrome, then my computer didn't swap to disk, and I could use it for days at a time (I leave my computers running). This is with no other apps open mind you.

Anyway, what does it matter what the numbers are if one is usable and another isn't?

I'm gonna leave this here, it seems to be turning into a browser war.