Skip to content

change: note that JS-initiated change does not trigger change event #617

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

Closed
wants to merge 1 commit into from

Conversation

arthurvr
Copy link
Member

@arthurvr arthurvr commented Jan 3, 2015

This would fix #345.

@@ -52,6 +52,9 @@ $( "#other" ).click(function() {
</code></pre>
<p>After this code executes, clicks on <samp>Trigger the handler</samp> will also alert the message. The message will display twice, because the handler has been bound to the <code>change</code> event on both of the form elements.</p>
<p>As of jQuery 1.4, the <code>change</code> event bubbles in Internet Explorer, behaving consistently with the event in other modern browsers.</p>
<div class="warning">
<p><strong>Note: </strong> dynamically changing the value of an input element, using <a href="/val"><code>.val()</code></a> for example, won't fire the event.</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The word "dynamically" is a little bit ambiguous here, since someone might interpret a user-generated change to be dynamic. Perhaps "Changing the value property of an input element using JavaScript..." instead?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. I'il update my PR this evening.

@arthurvr arthurvr force-pushed the PR-val-event-fix-345 branch 2 times, most recently from 7028bd0 to 6dedb28 Compare January 5, 2015 21:13
@arthurvr arthurvr force-pushed the PR-val-event-fix-345 branch from 6dedb28 to 3b3fbe2 Compare January 13, 2015 06:09
@arthurvr arthurvr force-pushed the PR-val-event-fix-345 branch from 3b3fbe2 to 833dad6 Compare January 22, 2015 20:46
@arthurvr
Copy link
Member Author

@dmethvin Does this LGTY now? I did the updates you asked for.

@dmethvin
Copy link
Member

I think the "changing" should be "Changing", otherwise good.

@arthurvr arthurvr closed this in 52a1b7d Jan 22, 2015
@arthurvr arthurvr deleted the PR-val-event-fix-345 branch January 22, 2015 21:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Note that JS-initiated change does not trigger change event
2 participants