Officially the only standard component that is allowed not to work anymore is the commandlink.
In JSF 1.2 the "JavaScript"lessness is part of the standard, because more and more applications must be accessable (== JS-free). Therefor we must check that as many components as possible can work with JS disabled. If they are not working without JS then the doc should say so... regards Alexander > -----Original Message----- > From: Mike Kienenberger [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 20, 2006 11:03 PM > To: MyFaces Discussion > Subject: Re: ALLOW_JAVASCRIPT > > On 7/20/06, ragsta <[EMAIL PROTECTED]> wrote: > > a simple question: does the ALLOW_JAVASCRIPT parameter work? > > > > Is very important for me that my site work even if the javascript is > > disabled on the user browser but turnig off the param > outputlink doesn't > > work more...even if the primary goal of turning off the > param is to change > > the behaviour of this command.... > > > > if this option is bugged I think I have to all back to a different > > framework... > > You will be very limited in what you can do if you disabled > javascript. > For instance, h:commandLink cannot work without javascript. > > Most of the interesting components also require javascript, as do a > lot of the common "tricks" for accomplishing tasks. > > You're probably better off not using JSF if you're not able > to allow javascript. >
