-
Notifications
You must be signed in to change notification settings - Fork 408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable IE's native input "clear" control, since it doesn't work properly. #153
Comments
@ZhouyangYe As I know, the input is controlled by the state of the component, so there is no way to programmatically clear the input, other than using |
@Tauka Oh, that's why, and the 'x' on IE does not notify when it is clicked, so there is no way to check if it's clicked. I've tried, onchange event can capture the value change when focus out, is it possible that when user focus out, the component get the value from Input element and update the state? |
@ZhouyangYe: Can you please provide a repro case/code example? It sounds like you might be passing in a value that is setting the selection. I can't repro your case in the example. |
@ericgio Hi, do you mean to reproduce the issue? I created a Typescript element with empty options and empty onchange function. Type in some value and clear it using the 'X' on IE. Then focus out by clicking somewhere else. The value is retained when focus out. |
@ZhouyangYe: a code example or jsfiddle would be helpful. |
@ericgio Can use the first example to test: http://ericgio.github.io/react-bootstrap-typeahead/ |
@ericgio It only happens on IE, with IE's default clear 'X'. |
Ah I see what you're saying now. That's expected behavior; all that's happening is the input value is being cleared, but the actual selections are not. See #34 for more context on why the component works this way. Use the I should disable the native IE control... |
@ericgio o, I see, thanks! |
Fixed in v1.2.0 |
Type in something to the field and clear it by clicking the 'x' sign on IE, then focus out by clicking somewhere else, the value retained.
The text was updated successfully, but these errors were encountered: