Hi, Leland-

>You might give W3C's validation page a try. It might give you a cue as to what might be wrong. It has caught many errors for me, and once you're page validates, you can be sure there is no problem in the html being streamed to the client's browser.

One of the add-ins for FireFox will validate the page, using a tool based on Tidy, which was developed by W3C. One of the very cool and useful things about FireFox, IMO, BTW, is it's add-in library. However, the pages in question have warnings, not errors, and none WRT the JavaScript. So, I think I'll need to pursue the machine.config and uplevel browser issue first.