Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Checkbox] "set checked" is triggering .change event
See original GitHub issueSemantic UI’s “set checked” fires a .change() trigger. This should not be the case according to the documentation
JSBin Example
Why this is bad: .click() doesn’t work for keyboard interactions on the checkbox, alienating many users, including those with visual disabilities.
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
jquery trigger change event on checkbox - Stack Overflow
In jQuery, you can usually trigger an event by calling it's eventhandler method withoud any function parameters. For example ...
Read more >Should $('#chk').prop('checked', true) trigger change event?
For a checkbox with a change event associated with it, shouldn't using prop() to change its checked state trigger its change() event?
Read more >jQuery checkbox change and click event | Edureka Community
(document).ready(function() { //set initial state. $('#textbox1').val($(this).is(' ... and keep textbox value consistent with the check ...
Read more >Changing .prop using jQuery does not trigger .change event
$('#button').click(function() { $('input[type="checkbox"][name="something"]').prop("checked", false); });. When I check the checkbox DO ...
Read more >checkbox change event jquery - Code Grepper
change checkbox jquery alert ... //set initial state. 3. $('#textbox1').val(this ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Does “stale” mean that this won’t be addressed? Just curious.
Fixed by https://github.com/fomantic/Fomantic-UI/pull/403 and supposed to be part of Fomantic-UI 2.7.2