Skip to content

Fix event target for input change events. Fixes #4288 #4311

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

Merged
merged 1 commit into from
Jul 9, 2015

Conversation

jimfb
Copy link
Contributor

@jimfb jimfb commented Jul 8, 2015

Fix event target for input change events. Fixes #4288

@chicoxyzzy
Copy link
Contributor

Will beta2 be released after merging this?

@jimfb
Copy link
Contributor Author

jimfb commented Jul 8, 2015

@chicoxyzzy Not sure, I'd really like to get the reconciler fix too before beta 2, but we'll see.

@zpao CR? This should be ready to go.

@jimfb
Copy link
Contributor Author

jimfb commented Jul 9, 2015

Ping @zpao

@zpao
Copy link
Member

zpao commented Jul 9, 2015

Threading that argument through is pretty annoying :(. Any other cases you missed?

@zpao
Copy link
Member

zpao commented Jul 9, 2015

Note for blame hunters (eg me): this is a regression due to #4150.

@jimfb
Copy link
Contributor Author

jimfb commented Jul 9, 2015

Hopefully not missing any others. I did a skim of the uses of nativeEvent, all of them looked reasonable (already have nativeEventTarget or don't need it in that situation).

jimfb added a commit that referenced this pull request Jul 9, 2015
Fix event target for input change events.  Fixes #4288
@jimfb jimfb merged commit 7b1f03f into facebook:master Jul 9, 2015
@vslinko
Copy link

vslinko commented Jul 21, 2015

@zpao do you have plans for beta2?

@zpao
Copy link
Member

zpao commented Jul 21, 2015

Ship it at some point

Edit: sorry, didn't read who asked that (thought it was a teammate who I could be a smart-ass to 😜). I was thinking we'd push out a beta2 sometime soon, maybe this week or next - want to get a few more things in order first.

@richardaday
Copy link

+1 on beta2

This bug seems common enough to block most apps immediately after installing to 0.14.0-beta1

@jimfb
Copy link
Contributor Author

jimfb commented Jul 22, 2015

@vslinko @richardaday It's not an officially supported/stable solution, but https://www.npmjs.com/package/react-dom-future stays up-to-date and has these fixes merged. It's what I use for my own testing and stuff. Obviously don't use this in production, but it'll let you play with the latest and greatest features and then you can let us know when we broke things in trunk :).

@chicoxyzzy
Copy link
Contributor

@jimfb thank you!

@vslinko
Copy link

vslinko commented Jul 22, 2015

@jimfb 🤘

@sophiebits
Copy link
Collaborator

@jimfb We already have http://react.zpao.com/builds/master/latest/ which has the latest browser builds as well as the npm packages (.tgz). So you can run

npm install http://react.zpao.com/builds/master/latest/react-dom.tgz

or list that URL as the version spec in package.json. These are updated automatically by Travis.

@jimfb
Copy link
Contributor Author

jimfb commented Jul 22, 2015

Ok, great, that works too!

danharper added a commit to danharper/playing-with-react-and-redux that referenced this pull request Jul 28, 2015
@syranide
Copy link
Contributor

syranide commented Aug 5, 2015

Was this in beta2/3? I'm still seeing the same issue.

@sophiebits
Copy link
Collaborator

Should have been…

@syranide
Copy link
Contributor

syranide commented Aug 6, 2015

Compiling with React(+DOM) 0.14.0-beta3 and event.target === undefined on IE9 in onChange.

@zpao
Copy link
Member

zpao commented Aug 6, 2015

Well, the change definitely made it out. But perhaps it wasn't a complete fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants