QUOTE(MyNameHere @ May 22 2007, 11:41 AM)

Hi. I recently installed a new PC and I noticed a couple of strange things. Some of the HTML and scripts in webmail aren't working.
<input type="text" id="to" size="55" tabindex="2" class="fixed" name="to" value="" />
whereas when I check it on another PC, it shows:
<input type="text" id="to" size="55" tabindex="2" class="fixed" name="to" value="" onchange="expandField(this)" /><span id="expandingto" style="color:red;visibility:hidden;">Expanding...</span>
under IE7, XP-Pro here;
<TD align=left><INPUT class=fixed id=to tabIndex=2 size=55 name=to></TD>
<TD align=right><A onmouseover="window.status='Help'; return true;"
onclick="open_help_win('imp', 'compose-to'); return false;"
onmouseout="window.status='';"
and under FireFox 2.0.0.3, the following appears;
<td align="left"><input id="to" size="55" tabindex="2" class="fixed" name="to" value="" onchange="expandField(this)" type="text"><span id="expandingto" style="color: red; visibility: hidden;">Expanding...</span></td>
<td align="right"><a href="" onclick="open_help_win('imp', 'compose-to'); return false;" onmouseout="window.status='';"
Not only are these strings different between the browsers, but neither actually directly matches your sample either ....?????
QUOTE
I also think the main webmail page (in my case, the folders view) is not refreshing every 15 minutes like it does elsewhere.
As I mentioned in the subtitle, I am using IE7, WinXP Pro SP2 (latest patches), and a new installation of Symantec Norton Internet Security 2007 with add-on pack (ad blocking). But I have the same NIS 2007 settings on my other Win XP Pro PC that is working fine. The only difference seems to be IE6 vs IE7.
One of the things I'm also wondering about right now is the possibility of your NIS getting into the middle of things and 'doing something' to the 'active part' of the scripting. For example, here the IE7 jumped up a 'warning' on the fact that there was a 'scri_pt running' and did I want to allow it .... FF jumped up an 'error message' that the field 'could not be expanded' .... both actions caised by me typing in some characters into the To: field, then trying to capture the 'source' code so I could see if the page was actually re-written with due to 'data input' .... the mouse action to try to select stuff causing the 'action' to attempt to 'expand' the field with the text input at that point .. which did not match anything usable (I have no addresses stored)
Just recently having been 'forced' into IE7 under XP, I'm still trying to srt out these new oddities myself, so I don't know how much of that factors in directly here .... for example, in my sample code capture above, I am confused over the 'commands' showing up in upper case and the lack of 'quote' marks around some variable names ..... worst case, the code involved actually jumps to different code sections based on the browser identity, each section written to work around each browser's idiosyncracies .... If this is the case, then that would probably lead one back to the mode where code was structured to work around IE6 issues that IE7 'fixed' but IE7 still 'looks like' IE6 to the browser-checking part of the codebase .....
Confused you yet? <g> Believe me, this has been going on since the initial releases of the IE7 code (not ignoring that FF keeps changing some things along the way also) .... but having recently read the initial plans for the upcoming IE8 version, and Microsoft's (alleged) plan of requiring some sort of 'agreement' signed up to by web developers in order to "take full advantage of IE8's new features" ..... it sure doesn't seem like the browsers wars are anywhere near finished .....