Yup. In addition, I made the admin install the 8.01 update so I could implement a coldfusion.window.destroy tear down process, and hopefully not run into jvm memory problems. coldfusion.navigate did not really work, since it was not really updating the window content correctly. Now to contemplate the CF8 Cum. Hot Fix 3 potential cfimage issues. :)
> Thanks for sharing. It's these little idiosyncratic tidbits that make > this job so interesting and frustrating all at once. > > -- > Mark Atkinson > AOCS Web | www.aocs.org > 217-693-4839 > > > > Robert Bell wrote: > Problem SOLVED. Seems by using the full path to the url, some > browsers were having problems, so I just used the cfimage.cfm relative > path, and everything works on all browser permutations just dandy. > Guess this was viewed as a cross-domain scripting attack somewhere > down the ajax/ui/cf/javascript path ? Hrm, anyway thanks for > listening to me at all. :) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:327217 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
