On Thu, Mar 26, 2009 at 5:15 PM, Charles Coleman <ccole...@email.unc.edu> wrote: > It looks like the relevant render method in the 5.0.18 source is final; so > it seems that my only recourse is to make my own custom component, or > perhaps to use a litttle Javascript to put some dummy content in that field. > Is that right?
Yes. The most reusable way to do that is to create a mixin that adds the needed JavaScript. > The PasswordField is in a BeanEditor, and I'm not even sure if I can get the > element ID to try an adhoc JavaScript trick. Implementing it as a mixin solves the problem. In this case, as you'll not use a vanilla PasswordField, you would need to overwrite the edition block for in each BeanEditor instance or create a new edition block for password fields. You would need to create a new DataTypeAnalyzer for this, I guess. -- Thiago --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
