>>Typical of HTML programming it gets cached and doesn't want to reload. That's the main reason I use the webpage-complete trick. It let's me see that it's actually been updated.
>
>John,
>
>I don't really do any web programming, but I like to "bookmark" some of these web discussions for my .NET Tips column in the UT's .NET Magazine .... so I gotta ask:
>
>What is this "webpage-complete trick" you mention?
>
>~~Bonnie

I don't do that much web either, more like I dabble in it from time to time.

When you do a save as from IE and select "Webpage, Complete" under "Save as type:" it saves the page and creates a directory of the same name. In the directory you can find the .js, .css and image files that are being downloaded for the page.

It's useful for checking that you are getting the expected versions of things, instead of a cached version. And I also sometimes use it to tweak a problem style sheet or page without having to mess with the real thing.

Not that much of a trick, but I find it really useful when I'm debugging something.