>>Javascript settings in the browser are as they have been for years through many versions. Each new install or upgrade just inherits the previous install settings. I have made no changes to these settings.
>
>In your case, this is a different situation. The HTML sent is not intercepted. You are receiving the HTML ok. The concern you mention is about not seeing new messages in the map window. Basically, on those two situations, you did not get any content at all in the map window.
>

Correct. The page appears as if I had hit the 'New messages for this session' icon and there were none pending, with both top and bottom frames empty.

>This is happening is there are no new message. However, in your case, you believe there should be, and you are probably right, if you are logging in after a while. Because, new messages are coming on a regular basis here. What can cause this is a double click on the login button. If a double click is done fast on the login button, this means that everything is processed ok but the last click will do a login and will overwrite everything that is being sent to your browser. Thus, the browser will show you the result from the last click. So, basically, the forum environment was sent with the new messages but by the time it was received, the last click was being sent and it showed empty.
>
>If you are sure you did not click twice by mistake on the login button, then this could have been because of a memory problem or something that was running instensively on the CPU which could have cause such a bad reaction.
>

Fairly sure no double click involved here, but you may be onto something. There was a long delay on loading the page, which might be explained by the browser somehow going back to you in some manner and the page reloading, with no new messages and hence the blank page. Still sounds like a script problem. Please tell me what script runs on the initial page load so I can look at it!

>What do you think?
>

I think we go through this every time you update your infrastructure ;-)

>However, the other issue when you did not get the javascript message is not correct. Your browser should have displayed the javascript message ok. I just don't know why you got that one however. I would assume that was caused by a bad connectivity at that time and the data was not fully received.
>

Just to test that, I have enabled all Javascript options in the browser. I am sure I'll regret that.

>I don't know if both situations were caused by the new update of that browser. If you continue to have problem with it, I would suggest you use Internet Explorer just for the Universal Thread, for a certain time, to see if things would work better.
>

That ain't happening.

>The errors about the stylesheet are not a factor in those situations. I will try to fix them however.

OK.