A couple of days ago, I upgraded Internet Explorer on the laptop from my work. Initially, everything seemed fine... Until I wanted to access our web-based HR system (PeopleSoft).
In the good-old-days, this website worked (not good, and not bad). Since IE7, the login page remains blank, while the sourcecode of the page is fully loaded. So no way of logging to my personal HR page. I have no idea what's causing this (PeopleSoft or IE7). I do know that the (simple) login page holds a gazillion lines of Javascript.... Why? It's just a login page.
A temporary work-around is using FireFox 2.0. Version 2.0 seemed to have solved some of the bugs I got with FireFox 1.5.x in PeopleSoft. Problem is that I need to change proxy settings for FireFox. I use IE for intranet browsing, because the developpers are MS-fans, and FireFox for global Internet browsing.
Mind you that you have to disable the NoScript extension for FireFox (when installed). Just allowing all scripts for the PeopleSoft website gives erratic behavior, and lot's of errors on the pages. Only disabling the extension seems to work (which requires a reboot :( ).
Anyway, somebody has to do some work to improve things.
In the good-old-days, this website worked (not good, and not bad). Since IE7, the login page remains blank, while the sourcecode of the page is fully loaded. So no way of logging to my personal HR page. I have no idea what's causing this (PeopleSoft or IE7). I do know that the (simple) login page holds a gazillion lines of Javascript.... Why? It's just a login page.
A temporary work-around is using FireFox 2.0. Version 2.0 seemed to have solved some of the bugs I got with FireFox 1.5.x in PeopleSoft. Problem is that I need to change proxy settings for FireFox. I use IE for intranet browsing, because the developpers are MS-fans, and FireFox for global Internet browsing.
Mind you that you have to disable the NoScript extension for FireFox (when installed). Just allowing all scripts for the PeopleSoft website gives erratic behavior, and lot's of errors on the pages. Only disabling the extension seems to work (which requires a reboot :( ).
Anyway, somebody has to do some work to improve things.