Make sure you check all the settings every time you run, e.g. which browsers to test (keep to a minimum to start), and whether you need Java installed. It does not remember any of your settings from the previous run.
One limitation is if you run a signed Applet, all you will see in the request to ok to run outside the sandbox. This is a necessary limitation. The Browsershots people can’t very well let signed rogue Applets destroy their hard disks.
To prepare a page for browsershotting, you might want to embed a large thumbnail jpg on it, showing roughly what the page is supposed to look like. That thumbnail will always render properly. That will make it easier to pick out any anomalies in the rendering on any specific browser, e.g. images without transparent backgrounds, missing elements… It will also help others viewing your page who don’t know what the page is supposed to look like. Alternatively, you could embed some text that points out what the rendering is supposed to look like.
You might use it for example to check out PNG (Portable Network Graphics) support in various browsers by looking at the renderings of page http://mindprod.com/jgloss/png.html.
You can pay a month for priority processing. It can take quite a while for your request to be processed otherwise. You have to keep manually extending your request to keep it alive until it is processed.
available on the web at:
optional Replicator mirror
Your face IP:[220.127.116.11]
|Feedback||You are visitor number 11.|