Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6389921
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 25, 20262026-05-25T03:27:51+00:00 2026-05-25T03:27:51+00:00

Background I have been using Backbone.js for some time and one aspect of it

  • 0

Background

I have been using Backbone.js for some time and one aspect of it that impresses me is how it allows me to simplify, abstract and reuse DOM elements as ‘views’. I have tried to read through some of the annotated source and am familiar with JQuery, but have little knowledge of how the DOM works on a deeper level.

Question

How does Backbone.JS tie DOM elements to views without assigning an id, class or other attribute to them?

i.e.

<ul>
  <li>Item one</li>
  <li>Item two</li>
  <li>Item three</li>
</ul>

I love that Backbone does this and would like to know how it does it!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-25T03:27:51+00:00Added an answer on May 25, 2026 at 3:27 am

    In javascript, a variable can hold a reference (i.e a programmatic thing that “refers to”) to some element of the DOM, which is just a Javascript object. Backbone makes sure that for a view, at least that element exists. For example, in jQuery, when you refer to the third item in your list:

    var item3 = $('ul li').eq(2);
    

    (It’s a zero-offset list, the first item is at index 0, the third at index 2), you can now change the text from “Item three” to “Item three point one four one five nine” with ordinary jQuery DOM manipulators:

    item3.text("Item three point one four one five nine");
    

    Even though that list item doesn’t have any particular class or ID attributes.

    A backbone view’s el field contains a constant reference to the parent element in which that view renders all of its stuff. Backbone uses the jQuery delegate event manager to attach a generic event handler to that one constant reference. Whenever an event happens within that DOM element or any of its children, the delegate catches the event, along with a reference to the specific DOM object within the parent el that created the event, and backbone uses some fairly standard jQuery magic to map that to an event handler in the view.

    It is, indeed, very cool stuff.

    I should add that the “constant”-ness of the el reference is, er, arguable. If you’re attaching view logic to an existing HTML element, you do assign to the el once, in the view’s initialize(). Javascript doesn’t enforce any notion of constantness, but you should only directly assign to el (ie this.el = something()) if you’re sure you know what you’re doing.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Some Background I have been using Git for a while now. The projects that
This is some background to my problem... I have been using 3rd Party as
Background: I am one of two developers on our team. We have been using
I come from a Java background and have been using C# for the last
Background: We have an application that has been in the works for over a
Background I have been using the Authorize.net SDK in an Eclipse project of it's
I have been working with changing the background colour of an element using css3
Background I have been now using Entity Framework + Linq for about year and
For my last few projects I have been using some of the utility files
The Background: I have been creating a script that based on input csv's that

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.