The reason for this is indeed what you say. I have a form that is getting wild and hairy, extremely unwieldy, so I want to immediately fork out which component I displayed called depending on whether js was enabled.
Amiri BenRifkah Bergsten-Buret-2 wrote: > > It sounds like you want your site to behave differently if the user > has JavaScript enabled. If you're really going for unobtrusive > JavaScript then your server side Mason code doesn't need to get > involved in the JavaScript enabled/disabled decision at all. Since > unobtrusive JavaScript is only supposed to enhance the functionality > of the site and not implement critical path functionality its > availability should only come into play on the client side and not in > the Server side Mason code. > -- View this message in context: http://www.nabble.com/Returning-a-*Variable*-From-Ajax--tp17111416p17138550.html Sent from the Perl Mason - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
