-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[FIX #14628] Don’t use preventDefault() on IE unless the user pressed enter #14667
Conversation
This also needs to be implemented in |
const value = Number(_.get(e, 'target.value', defaultValue)); | ||
if (_.isFunction(handleChange)) { | ||
return handleChange({ [name]: value }); | ||
} | ||
}; | ||
}; | ||
|
||
function detectIE() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this be a library that's shared in both files?
@simianhacker updated |
@@ -1,10 +1,14 @@ | |||
import _ from 'lodash'; | |||
import detectIE from './is-ie'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you change this to work like
import { isIE } from './is_ie';
or
import { detectIE } from './detect_id';
We stopped relying on exporting defaults and we also use snake case for all our filenames.
@@ -0,0 +1,25 @@ | |||
export default function detectIE() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't export default... just export the function name.
fixed and fixed |
LGTM... Make sure and back port to 6.0 and 6.x |
backported to 6.0 and 6.x (c805c3b) |
I reopened the issue #14628 because I'm still seeing the same behavior on the 6.0.0 BC1 build from yesterday. |
This PR fixes issue #14628
React 15.x has issues with
event.preventDefault()
in ie, while one of those issues is fixed in 15.6.1, the other (facebook/react#7281) is not. This PR is a patch to work around the issue until kibana moves to react 16.xTested in: