[S2] Simple-ish tag question about autocomplete

[Skip Hollowell <sk...@skipdaddy.com>]

In my app, I don't want to have any of the fields be autocomplete, so I 
took the generalized approach of each form calling an onload script that 
sets AUTOCOMPLETE=OFF.  Turns out, this gets my security folk's knickers 
in a twist, and they would like field itself have AUTOCOMPETE set to 
off, so people who turn off Javascript aren't able to bypass this concern.

But I can't figure out how to, using regular struts stags, to add a 
parameter that isn't in the tag definition.  Any ideas?


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

Re: [S2] Simple-ish tag question about autocomplete

[Dave Newton <ne...@yahoo.com>]

--- Skip Hollowell <sk...@skipdaddy.com> wrote:
> In my app, I don't want to have any of the fields be autocomplete, so I 
> took the generalized approach of each form calling an onload script that 
> sets AUTOCOMPLETE=OFF.  Turns out, this gets my security folk's knickers 
> in a twist, and they would like field itself have AUTOCOMPETE set to 
> off, so people who turn off Javascript aren't able to bypass this concern.
> 
> But I can't figure out how to, using regular struts stags, to add a 
> parameter that isn't in the tag definition.  Any ideas?

The quickest might just be to modify the form field templates for whatever
theme you're using. Otherwise you'd have to modify the TLD and go through the
bother of adding an actual parameter to the tags, and that's surprisingly
irritating. And you'd have to modify the templates anyway.

If it's an always-on/site-wide kind of thing I'd just extract and modify the
templates.

Dave


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org