Skip to content

one(): Fix description of behavior for delegated .one() events #519

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
Closed

one(): Fix description of behavior for delegated .one() events #519

wants to merge 1 commit into from

Conversation

tomfuertes
Copy link
Contributor

Refs #489 (specifically #issuecomment-42754794) and updates the preceding paragraph appropriately.

@@ -44,13 +44,13 @@
</argument>
</signature>
<longdesc>
<p>The first form of this method is identical to <code>.bind()</code>, except that the handler is unbound after its first invocation. The second two forms, introduced in jQuery 1.7, are identical to <code>.on()</code> except that the handler is removed after the first time the event occurs at the delegated element, whether the selector matched anything or not. For example:</p>
<p>The first and second forms of this method are respectively identical to <code>.bind()</code> and <code>.on()</code>, except that the handler is unbound in each after its first invocation. For example:</p>
Copy link
Member

Choose a reason for hiding this comment

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

I think we can drop the comparison to .bind() altogether and instead just have: "The .one() method is identical to .on(), except that…"

Refs #489 (specifically #issuecomment-42754794) and updates the preceding paragraph appropriately.
@tomfuertes
Copy link
Contributor Author

@kswedberg - Love it!

Rebased w/ feedback + removed now redundant second code block.

@kswedberg kswedberg closed this in fd3b18b Jul 10, 2014
@kswedberg
Copy link
Member

Excellent. Thanks for taking care of this!

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.

2 participants