Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fixes #1038 - Document changes to view.$. #1040

Merged
merged 1 commit into from Feb 25, 2012
Merged

Fixes #1038 - Document changes to view.$. #1040

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
7 changes: 6 additions & 1 deletion index.html
View file
Open in desktop
Expand Up @@ -533,6 +533,11 @@ <h2 id="upgrading">Upgrading to 0.9</h2>
Similarly, after changing an attribute silently, that <tt>change:attribute</tt>
event <i>will</i> fire during the next change.
</li>
<li>
Since <tt>view.$(selector)</tt> is now equivalent to <tt>view.$el.find(selector)</tt>
rather than <tt>$(selector, view.el)</tt> it can no longer be used when
<tt>selector</tt> is an HTML string or DOM element.
</li>
</ul>

<h2 id="Events">Backbone.Events</h2>
Expand Down Expand Up @@ -2092,7 +2097,7 @@ <h2 id="View">Backbone.View</h2>
<b>$</b> function that runs queries scoped within the view's element. If you use this
scoped jQuery function, you don't have to use model ids as part of your query
to pull out specific elements in a list, and can rely much more on HTML class
attributes. It's equivalent to running: <tt>$(selector, this.el)</tt>
attributes. It's equivalent to running: <tt>view.$el.find(selector)</tt>
</p>

<pre>
Expand Down