React checkbox will not work, onChange does not fire











up vote
1
down vote

favorite












I have checked various forums to resolve this issue, but I could not find an example where the poster had literally copy and pasted from React docs.



I have included a snippet of my code.



When I hover over the checkbox it goes berserk and has seizure (almost like flashing). When I click it, I do not believe onChange fires, because there is no output to the console. The checkbox code was copied and pasted directly from https://reactjs.org/docs/forms.html.



If I manage to click the checkbox during its flashing fit the entire disappears.



Any help will be appreciated. I am hoping this has been ansered elsewhere, I just can't seem to find it.



class LoginPage extends React.Component {
constructor(props) {
super(props);

this.state = {
username: '',
password: '',
submitted: false,
isGoing: true,
};

this.handleInputChange = this.handleInputChange.bind(this);
}


handleInputChange(event) {
console.log("handle input change")
const target = event.target;
const value = target.type === 'checkbox' ? target.checked : target.value;
const name = target.name;

this.setState({
[name]: value
});
}


render() {

return (
<span>
<input
name="isGoing"
type="checkbox"
checked={this.state.isGoing}
onChange={this.handleInputChange}
/>
<label>Checkbox</label>
</span>
);


I don't think this should make a difference, but I am using redux for much of my apps state.



Thanks!










share|improve this question


















  • 2




    It seems to work fine. What environment are you coding in?
    – Tholle
    Nov 9 at 18:24










  • Could it be that the parent component has events that somehow interfere with the LoginPage?
    – Ole EH Dufour
    Nov 9 at 18:46










  • @Tholle. My environment is React on unix. I wish I could give more details. The project is fairly big with various input examples with values dependent on both component state and redux state. The oddest thing is the "seizure" when I hover over the checkbox. It is possible to click the box and then correct response occurs. It is just clear that something is broken because of the behavior.
    – nbaughn
    Nov 12 at 17:16















up vote
1
down vote

favorite












I have checked various forums to resolve this issue, but I could not find an example where the poster had literally copy and pasted from React docs.



I have included a snippet of my code.



When I hover over the checkbox it goes berserk and has seizure (almost like flashing). When I click it, I do not believe onChange fires, because there is no output to the console. The checkbox code was copied and pasted directly from https://reactjs.org/docs/forms.html.



If I manage to click the checkbox during its flashing fit the entire disappears.



Any help will be appreciated. I am hoping this has been ansered elsewhere, I just can't seem to find it.



class LoginPage extends React.Component {
constructor(props) {
super(props);

this.state = {
username: '',
password: '',
submitted: false,
isGoing: true,
};

this.handleInputChange = this.handleInputChange.bind(this);
}


handleInputChange(event) {
console.log("handle input change")
const target = event.target;
const value = target.type === 'checkbox' ? target.checked : target.value;
const name = target.name;

this.setState({
[name]: value
});
}


render() {

return (
<span>
<input
name="isGoing"
type="checkbox"
checked={this.state.isGoing}
onChange={this.handleInputChange}
/>
<label>Checkbox</label>
</span>
);


I don't think this should make a difference, but I am using redux for much of my apps state.



Thanks!










share|improve this question


















  • 2




    It seems to work fine. What environment are you coding in?
    – Tholle
    Nov 9 at 18:24










  • Could it be that the parent component has events that somehow interfere with the LoginPage?
    – Ole EH Dufour
    Nov 9 at 18:46










  • @Tholle. My environment is React on unix. I wish I could give more details. The project is fairly big with various input examples with values dependent on both component state and redux state. The oddest thing is the "seizure" when I hover over the checkbox. It is possible to click the box and then correct response occurs. It is just clear that something is broken because of the behavior.
    – nbaughn
    Nov 12 at 17:16













up vote
1
down vote

favorite









up vote
1
down vote

favorite











I have checked various forums to resolve this issue, but I could not find an example where the poster had literally copy and pasted from React docs.



I have included a snippet of my code.



When I hover over the checkbox it goes berserk and has seizure (almost like flashing). When I click it, I do not believe onChange fires, because there is no output to the console. The checkbox code was copied and pasted directly from https://reactjs.org/docs/forms.html.



If I manage to click the checkbox during its flashing fit the entire disappears.



Any help will be appreciated. I am hoping this has been ansered elsewhere, I just can't seem to find it.



class LoginPage extends React.Component {
constructor(props) {
super(props);

this.state = {
username: '',
password: '',
submitted: false,
isGoing: true,
};

this.handleInputChange = this.handleInputChange.bind(this);
}


handleInputChange(event) {
console.log("handle input change")
const target = event.target;
const value = target.type === 'checkbox' ? target.checked : target.value;
const name = target.name;

this.setState({
[name]: value
});
}


render() {

return (
<span>
<input
name="isGoing"
type="checkbox"
checked={this.state.isGoing}
onChange={this.handleInputChange}
/>
<label>Checkbox</label>
</span>
);


I don't think this should make a difference, but I am using redux for much of my apps state.



Thanks!










share|improve this question













I have checked various forums to resolve this issue, but I could not find an example where the poster had literally copy and pasted from React docs.



I have included a snippet of my code.



When I hover over the checkbox it goes berserk and has seizure (almost like flashing). When I click it, I do not believe onChange fires, because there is no output to the console. The checkbox code was copied and pasted directly from https://reactjs.org/docs/forms.html.



If I manage to click the checkbox during its flashing fit the entire disappears.



Any help will be appreciated. I am hoping this has been ansered elsewhere, I just can't seem to find it.



class LoginPage extends React.Component {
constructor(props) {
super(props);

this.state = {
username: '',
password: '',
submitted: false,
isGoing: true,
};

this.handleInputChange = this.handleInputChange.bind(this);
}


handleInputChange(event) {
console.log("handle input change")
const target = event.target;
const value = target.type === 'checkbox' ? target.checked : target.value;
const name = target.name;

this.setState({
[name]: value
});
}


render() {

return (
<span>
<input
name="isGoing"
type="checkbox"
checked={this.state.isGoing}
onChange={this.handleInputChange}
/>
<label>Checkbox</label>
</span>
);


I don't think this should make a difference, but I am using redux for much of my apps state.



Thanks!







javascript reactjs checkbox input onchange






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 9 at 18:21









nbaughn

61




61








  • 2




    It seems to work fine. What environment are you coding in?
    – Tholle
    Nov 9 at 18:24










  • Could it be that the parent component has events that somehow interfere with the LoginPage?
    – Ole EH Dufour
    Nov 9 at 18:46










  • @Tholle. My environment is React on unix. I wish I could give more details. The project is fairly big with various input examples with values dependent on both component state and redux state. The oddest thing is the "seizure" when I hover over the checkbox. It is possible to click the box and then correct response occurs. It is just clear that something is broken because of the behavior.
    – nbaughn
    Nov 12 at 17:16














  • 2




    It seems to work fine. What environment are you coding in?
    – Tholle
    Nov 9 at 18:24










  • Could it be that the parent component has events that somehow interfere with the LoginPage?
    – Ole EH Dufour
    Nov 9 at 18:46










  • @Tholle. My environment is React on unix. I wish I could give more details. The project is fairly big with various input examples with values dependent on both component state and redux state. The oddest thing is the "seizure" when I hover over the checkbox. It is possible to click the box and then correct response occurs. It is just clear that something is broken because of the behavior.
    – nbaughn
    Nov 12 at 17:16








2




2




It seems to work fine. What environment are you coding in?
– Tholle
Nov 9 at 18:24




It seems to work fine. What environment are you coding in?
– Tholle
Nov 9 at 18:24












Could it be that the parent component has events that somehow interfere with the LoginPage?
– Ole EH Dufour
Nov 9 at 18:46




Could it be that the parent component has events that somehow interfere with the LoginPage?
– Ole EH Dufour
Nov 9 at 18:46












@Tholle. My environment is React on unix. I wish I could give more details. The project is fairly big with various input examples with values dependent on both component state and redux state. The oddest thing is the "seizure" when I hover over the checkbox. It is possible to click the box and then correct response occurs. It is just clear that something is broken because of the behavior.
– nbaughn
Nov 12 at 17:16




@Tholle. My environment is React on unix. I wish I could give more details. The project is fairly big with various input examples with values dependent on both component state and redux state. The oddest thing is the "seizure" when I hover over the checkbox. It is possible to click the box and then correct response occurs. It is just clear that something is broken because of the behavior.
– nbaughn
Nov 12 at 17:16

















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53231348%2freact-checkbox-will-not-work-onchange-does-not-fire%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53231348%2freact-checkbox-will-not-work-onchange-does-not-fire%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Schultheiß

Verwaltungsgliederung Dänemarks

Liste der Kulturdenkmale in Wilsdruff