-1 for me. Why should we give special attention to this one particular attribute and not others, especially considering the autocomplete attribute isn't even in the HTML spec?
Besides, for the times I've needed it I just put the attribute right in the HTML. I'm having a tough time imagining why you'd want this under programmatic control. jk On Wed, Nov 12, 2008 at 09:18:18AM -0800, [EMAIL PROTECTED] wrote: > Does anybody else thinks this is an interesting feature to be added? If > yes, I will submit a patch. > > Thanks, > Bruno > > On Nov 12, 2008 11:21am, James Carman <[EMAIL PROTECTED]> wrote: > >Ahhhh, sorry. > > > > > > > >On Wed, Nov 12, 2008 at 8:16 AM, wrote: > > > >> That's for Ajax... > > > >> > > > >> I'm talking about the attribute 'autocomplete' that browsers handle by > > > >> themselves. > > > >> > > > >> > > > >> > > > >> On Nov 12, 2008 11:11am, James Carman wrote: > > > >>> > > > >>> Have you tried using AutoCompleteTextField? > > > >>> > > > >>> > > > >>> > > > >>> On Wed, Nov 12, 2008 at 8:08 AM, wrote: > > > >>> > > > >>> > I'm finding myself coding the same code over and over, on different > > > >> > > > >> projects > > > >>> > > > >>> > (for different customers), having to provide a subclass of TextField > > > >> > > > >> with an > > > >>> > > > >>> > option to setAutocomplete(boolean) where it will add(or not) the > > > >>> > > > >>> > 'autocomplete' tag for during the componentTag method - > > > >>> > > > >>> > saving from creating an instance of AttributeModifier > > > >>> > > > >>> > > > > >>> > > > >>> > What about adding that to TextField? > > > >>> > > > >>> > > > > >>> > > > >>> > Regards, > > > >>> > > > >>> > Bruno > > > >>> > > > >>> > > > > >>> > > > >> > >
