-
Notifications
You must be signed in to change notification settings - Fork 480
Expand "Triggering Event Handlers" article #84
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
Labels
Comments
great stuff! also for |
I have begun work on this here. I think that I need to read more examples to see how much detail is appropriate. |
johnkpaul
added a commit
to johnkpaul/learn.jquery.com
that referenced
this issue
Apr 12, 2012
This looks good. Planning on expanding it @johnkpaul? |
I just updated my pull request to include your feedback, @addyosmani. There's nothing that I'm planning to add. |
addyosmani
added a commit
that referenced
this issue
May 21, 2012
Added triggering handlers section. Initial work for #84
arthurvr
pushed a commit
to arthurvr/learn.jquery.com
that referenced
this issue
Jan 4, 2015
arthurvr
pushed a commit
to arthurvr/learn.jquery.com
that referenced
this issue
Jan 4, 2015
…lers Added triggering handlers section. Initial work for jquery#84
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In addition to the basic content there now on
$.fn.trigger
, the article should cover the following$.fn.triggerHandler
- the difference between it and$.fn.trigger
(only calls bound handlers, not default behaviour)$.fn.trigger
to control your application - discussing why apps should have direct access to call necessary methods, instead of triggering anonymous handlers bound all over the DOM. (i.e., your "view" should be bound to call application methods, your application shouldn't dig into the DOM to make itself happen)The text was updated successfully, but these errors were encountered: