Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Strange componentWillReceiveProps behaviour #2666

Closed
AndrewGrachov opened this issue Dec 5, 2014 · 2 comments
Closed

Strange componentWillReceiveProps behaviour #2666

AndrewGrachov opened this issue Dec 5, 2014 · 2 comments
Labels
Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug

Comments

@AndrewGrachov
Copy link

screenshot -
https://yadi.sk/i/l90baQ8QdBTnW

thing is, props.selected is undefined if type in console by hand, but chrome console suggest(e.g. type sel, then arrow-right) shows proper 'node18n' value.

hasOwnProperty

condition fails.

This thing is blowing my mind. I suggest something wrong with getters/setters let me know if you know teh root of teh problem
@aackerman
Copy link
Contributor

What version of React are you using?

What's the smallest amount of code you can use to reproduce what you're seeing here?

@zpao zpao added the Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug label Dec 10, 2014
@jimfb
Copy link
Contributor

jimfb commented Oct 26, 2015

Unconfirmed for nearly a year, closing this out. Please open a new issue with a reproducible testcase if you believe this bug still exists.

@jimfb jimfb closed this as completed Oct 26, 2015
This was referenced Apr 12, 2023
Open
Open
Open
Open
Open
@nchathu2014 nchathu2014 mentioned this issue Sep 7, 2023
Open
@andygongea andygongea mentioned this issue Sep 7, 2023
Open
@leftrightleft leftrightleft mentioned this issue Sep 7, 2023
Open
@saurabharch saurabharch mentioned this issue Sep 7, 2023
Open
@Matthelonianxl Matthelonianxl mentioned this issue Sep 8, 2023
Open
@Matthelonianxl Matthelonianxl mentioned this issue Nov 30, 2023
Open
@saurabharch saurabharch mentioned this issue Dec 1, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@zpao @aackerman @AndrewGrachov @jimfb