found out there is a documented problem that IE does not fire onchange
listeners with auto complete. Perhaps we should code around this in
Trinidad by using a combination of onblur and onfocus?

-Andrew

On Tue, Feb 19, 2008 at 8:01 AM, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> Hi,
>
>
>  On Feb 19, 2008 3:56 PM, Richard Yee <[EMAIL PROTECTED]> wrote:
>  > Is there a way to output 'autocomplete="off"' in a form or inputText
>  > element? Since IE, Firefox and Safari do not an onChange JavaScript
>  > event if the user picks a item from the browser's autocomplete list.
>  > This is causing a problem in my application because I am using
>  > autosubmit=true and have a valueChangeListener on an inputText. The
>  > valueChangeListener does not get invoked in the case where the user
>  > chooses an item from the autocomplete list and tabs out of the control.
>
>  yes, there is an odd browser bug regarding this. IMO we should finally
>  address the
>  already in the past suggest attribute "autocomplete"
>  autocomplete="off" (on=> default).
>
>  JSF 1.2 was introducing this on <h:inputText>
>
>  -Matthias
>
>
>
>  >
>  > -R
>  >
>  > Richard Yee wrote:
>  > > It seems that this is a problem with IE 6,Firefox 2.0.0.11
>  > > <http://2.0.0.11>, and Safari 3.0.4. I tested FireFox and Safari on a
>  > > MacBook Pro
>  > >
>  > > http://jehiah.cz/archive/onchange-and-autocomplete
>  > >
>  > > The behavior that I see is that value change events work fine if the
>  > > user types in a value or pastes a value in to an tr:inputText and then
>  > > tabs to another component. If the user has previously submitted a
>  > > value in the inputText and then begins typing a value that starts with
>  > > the same characters and then selects an entry in the autocomplete list
>  > > that appears and then tabs out of the component, no onChange gets
>  > > fired and as a result, no valueChangeEvent occurs on the server.
>  > >
>  > > Is it possible to output a autocomplete="off" in the tr:form?
>  > >
>  > > Does anyone have any idea of a workaround for this problem?
>  > >
>  > > Thanks,
>  > >
>  > > Richard
>  > >
>  > >
>  > >
>  > >
>  > > On Feb 15, 2008 12:59 PM, Richard Yee <[EMAIL PROTECTED]
>  > > <mailto:[EMAIL PROTECTED]>> wrote:
>  > >
>  > >     Yes, I realize that valueChangeEvents occur on the server. Yes,
>  > >     when I tested, I tabbed out of the control in both cases. I will
>  > >     check the behavior on Firefox.
>  > >
>  > >     -Richard
>  > >
>  > >
>  > >
>  > >     On 2/15/08, *Andrew Robinson* <[EMAIL PROTECTED]
>  > >     <mailto:[EMAIL PROTECTED]>> wrote:
>  > >
>  > >         value changes are on the server. Auto submit should work
>  > >         onblur, so shouldn't matter how you enter the data. You did
>  > >         tab off of the input text right?
>  > >
>  > >
>  > >         On Fri, Feb 15, 2008 at 1:36 PM, Richard Yee
>  >
>  > >         <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
>  > >
>  > >             Hi,
>  > >             It appears that valueChangeEvents are not triggered on the
>  > >             tr:inputText component when the user selects an entry
>  > >             using the AutoComplete feature of Internet Explorer. I
>  > >             have tested this on IE 6.0.2900.
>  > >
>  > >             In my JSP file I have this:
>  > >                     <tr:inputText label="Enter Value:"
>  > >             valueChangeListener="#{myBacking.inputTextChangeListener}"
>  > >                       autoSubmit="true" value="#{myBacking.textValue}"/>
>  > >
>  > >             I am getting valueChangeEvents when the user types a value
>  > >             in the textInput but I do not get an event if I select the
>  > >             value from the autocomplete box that IE presents if values
>  > >             have been entered previously into the field. Is there a
>  > >             way to output  autocomplete="off" in the rendered output
>  > >             for the tag or is there a fix to the javascript that
>  > >             detects the value change?
>  > >
>  > >             Thanks,
>  > >
>  > >             Richard
>  > >
>  > >
>  > >
>  > >
>  > >
>  >
>  >
>
>
>
>  --
>  Matthias Wessendorf
>
>  further stuff:
>  blog: http://matthiaswessendorf.wordpress.com/
>  sessions: http://www.slideshare.net/mwessendorf
>  mail: matzew-at-apache-dot-org
>

Reply via email to