CODEWITHSUNDEEP
javascriptjqueryhtml
8protons
8protons

Reputation: 3959

Should I be using classes more than ID's when utilizing jQuery?

As a new web developer, I've been utilizing a lot of resources like StackOverflow to assist me in the learning and development process.

When using jQuery, all of the examples/responses that I've come across so far have only referenced classes, like so:

$('.yourClass')

as opposed to

$('#yourID')

Seeing that class referencing seems to be the trend (I honestly haven't found one author who writes a jQuery to an ID), are there any pitfalls I should be aware of for using ID's w/ jQuery or JS in general? Thanks!

EDIT 1: I'm aware that ID's are for single-items, classes are for accessing multiple items. I'm more interested in why I don't see any jQuery or JS examples referencing ID's. Thank you!

Upvotes: 0

Views: 81

Answers (5)

Kevin B
Kevin B

Reputation: 95022

You would have to ask each author on a case-by-case basis, but generally when creating examples, the selector used doesn't matter; what's important is that you have a jQuery collection that you can call a method on.

By using a class selector in the example, you avoid newbie developers claiming that your plugin doesn't work when they try to use it on multiple elements with the same ID. Your example serves the purpose of showing how to use it on one or more elements, rather than just one.

Upvotes: 1

victorayub
victorayub

Reputation: 67

I know that you are fully aware of why we should use ID's or classes. But the vast majority of answers that are given here, are thinking of a project context.

So, let's say editing a .js file that is linked to the scope of the entire project, the idea here is to be as reusable as possible, so that's why you'll see much more classes references than ID's. Is hard to maintain a project js file that makes reference to different ID's that are abroad the project. Same thing will apply to css.

I hope the answer is enough, be free to post a comment or suggestions. :-)

Upvotes: 0

AGE
AGE

Reputation: 3792

Think of your HTML and CSS first.

Using Classes

If you have multiple HTML elements which all will look, feel and behave in the same way, then it is highly recommended to use a class to represent their style and behavior.

Example: rows or columns on a table, navigation buttons which animate in the exact same way, wrapper to images which have the same size throughout your website, etc.

Using ID's

However, if you have a unique HTML element which represents a particular thing or state or action in one of your pages, then that element should contain an id.

Example: pop up modal, a unique looking button, unique sections on your website which you can navigate to by their id, etc.

Then, you can use this behavior in your JavaScript and jQuery or whatever else you like to use.

Further reading

Upvotes: 0

Culyx
Culyx

Reputation: 539

An ID must be unique, you can have only one (like highlanders).

Classes are used to identify a "type" of object not a specific one.

An obligatory car analogy:
An ID is a license plate, unique to one specific thing #345-abc
The class relates to a whole category of things like .truck

Take note that a selector like $(".something") will actually be capable of producing a list of DOM elements; as it will select all DOM elements with the class of "something"

An ID selector $("#unique") will only ever return one element

Upvotes: 0

dave mankoff
dave mankoff

Reputation: 17779

People like to use classes because ids have to be unique across the whole page. When trying to make reusable, pluggable components, id's make this impossible to enforce.

Exception: the new web-components standard allows you to encapsulate ids to just your component.

Upvotes: 0

Related Questions