I certainly intend to look at Ext, and JQuery, when I get the chance. However, specifically with the CF8 Ext controls, what is 'best practice' for handling degradation? From my experience, javascript disabled cfpods don't show any content pulled from the source attribute, but do show content that's within the cfpod tags - I suppose you could duplicate content using both methods to allow for this?
Any other thoughts. Will -----Original Message----- From: James Holmes [mailto:[EMAIL PROTECTED] Sent: 14 February 2008 14:38 To: CF-Talk Subject: Re: CF8 Ajax features and javascript disabled ExtJS 2 has good features for creating these controls out of existing markup on the page - so if JS is disabled, the display is the standard HTML (divs etc) that would have formed the cool looking stuff. On Thu, Feb 14, 2008 at 10:17 PM, Will Swain <[EMAIL PROTECTED]> wrote: > Hi, > > What are people doing to allow for javascript being disabled/older > browsers when implementing some of the cf8 ajaxy goodness in their > apps. I'm thinking primarily the layout stuff like cfpod and tabbed > layouts but anything really? I'm using these tags more and more, and > liking the results alot, but this is a concern. Thoughts anyone? -- mxAjax / CFAjax docs and other useful articles: http://www.bifrost.com.au/blog/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;160198600;22374440;w Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:299001 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
