If Microsoft isn't going to accurately support the DOM in their web browser, they should consider renaming their functions to what they actually do. After beating my head against an IE problem (which has the worlds worst javascript debugger--motto: "What's a javascript debugger?"), I finally realized that when trying to do a document.getElementById(), if you don't have an element with the ID, but you do have one with the name, it'll try to be helpful and give you the one with the name--even though that one has a different ID.
They should consider renaming the function to getElementByIdOrNameDependingOnWhatIsAvailable().
A little insight into the networking between our office and the home office. We have a T1 to the internet. They have a T1 to the internet (for 50 people, but that's not really what this is about). We have a freeswan box on this end, they have a freeswan box on their end. IPSEC between the two.
The home office runs the gambit of Microsoft servers with no local replication of any of them. During the day, their T1 gets very saturated. Almost to the point of unusability.
For our email, we connect to the Exchange server out there--not necessarily a bad thing, but it is in this case. The problem arises when someone decides to email a largeish (in this case >500K) attachment.
Microsoft, in their infinate wisdom, has designed the Outlook/Exchange connection to be pretty tight where Outlook relys on the Exchange server for most everything. This hurts with large emails. When you click on the email to bring it up in the preview pane, it has to download the entire message and attachment. When you want to view the attachment, it has to redownload the attachment. If you accidentally click onto another message, you have to wait all over again.
Why can't they cache this stuff locally, and ask the exchange server if it has changed? MS has done some wonderful things with file transferring and caching with their BITS client, but I think that with road warriors and remote offices, they should look at optimizing some of their business applications.
Maybe I'll start using Outlook Web Access instead.
I just upgraded the MS Office on my windows machine to Office Professional 2003 and noticed something with Outlook 2003 that really is getting to be irritating. When replying to a message with multiple recipients, and doing a "Reply to All" Outlook 2003 decides to include me in the "To" field. I never had this problem with Outlook XP.
Any one of the 2 geeks that reads this know how to change this behavior? It's truly annoying.
UPDATE: Resolution found (since there seem to be a lot of people searching for this these days)