Q. Why don't you support any of the modern "standards" A.  It's a long story but a simple a simple answer. I view a technical standard is an established norm and not a requirement. Our spec it truly written to work on anybrowser and not some spec. Ours is the standard as it is the established norm. I know I won't convince anyone of this, but it's the reality as I see it. contact us Q. When I try to use the site viewer I end up on your home page. A.  There is a bit of code in the site viewer to insure it can only be used from our site as it does take up a large amount of bandwidth to run. Increasingly we are unable to determine if the viewer is being used from our site. It must have something to do with security. If this happen to you we suggest you try using through some other access method. Perhaps at work are at the library. Q. When I try to view my page I get a script error. A.  Our viewer gets very high usage. It's not really designed for such heavy usage so sometimes it can't take the heat. Just try again later when you suspect that the site would get a bit less use. Q. When I try to view my page I don‘t see anything. A.  Most likely it is because you are using frames. The viewer does not support frames. The use of frames just isn't a good idea in general. This does not have anything to do with compatibly. They just cause more problems then they solve. It's probably a good idea to see if you can get by without frames. If you must use frames make sure you provide content for browsers that don't support frames. To view the pages within your frames enter the address of the individual frames into the viewer to get an idea of what your site will look like. Q. I am using FrontPage 2002 and my pages look funny with the site viewer. A. FrontPage creates none backward compatible web sites. Your only choice is to use another tool to create your web site. Q. I tested my site with this browser, that browser and the other browser and everything works great. How come it has problems with your viewer? A. What you're doing is using what is called the empirical method of ensuring that your site is cross browser compatible. Do this work? Well sort of. The goal is to use a well-known subset of HTML that works across browsers and insure that it is well formed. The problem is if you are using some none standard tags or poorly formed tag then you're depending on the "error case" logic in the browser to solve the problem for you. Do browsers do a good job of this? You bet they do. The goal of a browser to try and make sense of your page no matter how poorly it's put together. But this means you really have to test your site on every browser on every platform to insure it "looks" right. There are no rules to say what should happen if something is wrong. The goal of our site viewer is to break your site. We are as picky as we know how to be. If a browser does not display correctly formed HTML in a consistent way across platforms then the creator of the browser will hear about that right away and more importantly be very likely to do something about it. Browser creators test endlessly against well formed HTML, but can only try so many error cases. After all the number of error cases is nearly endless. Q. My Graphics show as broken links A. We don't support as broad a range of graphic locating as a normal browser does. Although we support about 95% of the cases there are a few cases we don't support. If your graphics are linked to relative addresses meaning they are not in same directory as your html page, but in a directory with the page, it may under rare conditions show as a problem link. Don't worry about this, as it's just a problem with the viewer and not your site. Q. When I try to view my page with the setting for HTML 3.2 compatibility why don‘t my table backgrounds show up? I‘ve tested every 3.x - 4.x browser and they all support this. A. Strictly speaking the background attribute is not part of the 3.2 HTML spec. This is at the heart of the issue the AnyBrowser level iii spec was created to solve. The AnyBrowser level iii spec was designed to show your site as the real world level III browsers see it. I don't think there actually is a browser that adheres to the 3.2 HTML spec and is restricted to it. Browsers that support the 3.2 HTML spec all add a little extra. The AnyBrowser level iii spec provides the lowest common denominator of the level 3 browsers. To view your site use the AnyBrowser iii viewer instead. Now if your site does not view correctly it's time to start coding your site to the AnyBrowser level iii spec.