[iVox]

I've followed this thread and wish to add some technical input and insight into what's going on, and how to implement it most easily into vB.

In the HEADINCLUDE template at the bottom or top include this single line:

 
<meta content="BlendTrans(Duration=0.01)" http-equiv="Page-Exit" />

This is all you need, and it also follows a format all modern browsers can understand including XHTML DTD specifications which all the good templates utilize you can download here. I've successfully tested it on MSIE, Opera, Netscape and Firefox, latest release versions of each as of this writing.

Folks, that's all you need to do, and this is web developer trick that's been around for while, much like GZIP compression has been.

Technically speaking, as the article linked earlier in this thread explained, on page refreshes, i.e. form submissions and other redirects, this command helps the browser reduce screen flicker and can be exploited for fade effects as well. The value I'm using is the best universal value (after many others have tried this or that) and you just set it and forget it.

You only need the exit argument because flicker issues only occur on redirects or refreshes on the page that is displayed following the task. The other argument is necessary only if you're intentionally fading or other cosmetic effects to exploit this ability.

The references people have been making about AJAX and FAJAX is easy enough to explain. AJAX is code use to display dynamic content "in place" so as to avoid screen refresh and might even call scripts that run server side fetching content from a database. To the user, the screen just dynamically changes, i.e. tables moving around, Netflix like informational dialogs displaying on top of content, or Google customized home page where you can drag/drop content as you build the page.

FAJAX is a term developers use to describe the AJAX effect of dynamic content updating, without actually using AJAX code. It's faking it, hence the term FAJAX.

In truth this meta command is one of those many W3C header tags that are not intended to be universally supported but exist for developers of browsers and plugins who want to utilize such features to manipulate the browser's abilities.

Due to the fact it's technically unsupported, you might see this ability lost in future browser implementations and it might even corrupt wireless or other future Internet technologies if the DTD doesn't specify this command. Some programmer out there might not be smart enough to ignore it or exploit it.

But for most of us, it works great and such issues are not a concern. Enjoy.

-jim