Use CF to block problems with Google Accelorator

Explains some problems that developers are having with the Google Web Accelerator. The tools speeds up your surfing experience by trying to pre-fetch all the content for links on the page. That way whichever one you click it already has the content.

Sounds all fine and good except when that page is in the admin of a web app. Lets say you have a page that list your users with links to edit or delete them. It goes ahead and calls off those, and is kind enough to ingore the JS prompts to confirm user deletion.

Chris Charlton

Chris CharltonChris, Los Angeles' CSS & ActionScript guru, successfully cannonballed into web development in the late 90's. Always caught up with the latest in Flash, Dreamweaver, Fireworks, and XML, Chris authored premium articles for the largest Dreamweaver/Flash community (www.DMXzone.com) and produced WebDevDesign (iTunes featured), a popular Web Design & Development Podcast. Somewhere, Chris finds time to run an authorized Adobe user group focused around open source and Adobe technologies. Being a big community leader, Chris Charlton remains a resident faculty member of the Rich Media Insitute and lends himself to speak at large industry events, like JobStock, NAB, and FITC Hollywood.

Brain cycles from Chris are always Web Standards, Flash Platform, and accessibility.

See All Postings From Chris Charlton >>

Place your comment about Use CF to block problems with Google Accelorator




You must me logged in to write a comment
Comments

Be the first to place a comment