#1 India's Top IT Training Institute
×

About Uncodemy

Know more about who we are and what we stand for.

About Us

About Us

Discover our mission to equip individuals with essential IT skills and industry expertise.

Read More →
UnCodeMy Gallery

UnCodeMy Gallery

Explore highlights from our IT training sessions and success stories.

Read More →
Mentors

Mentors

Meet the industry experts who train and guide you through your course.

Read More →
Free Resources

Free Resources

Free tutorials, interview questions, tools and calculators to help you learn.

Explore →
×

Free Resources

Learn, practice and plan your career — bilkul free.

Tutorials

Tutorials

Step-by-step written tutorials to learn any technology at your own pace.

Read More →
Free Counselling

Free Counselling

Book a free video counselling session and pick the right course for you.

Read More →
Online Compiler

Online Compiler

Write, run and test your code online — no setup required.

Read More →
jQuery

jQuery Traversing

Traversing in jQuery means moving from elements you already selected to related elements in the DOM tree: up to parents, down to children, or sideways to siblings. Instead of writing a new selector from scratch, you start from something you have, often the element that was clicked, and walk to the element you actually need. This makes code shorter and keeps it working when the same component appears many times on a page.

Moving up the tree

  • .parent() returns the direct parent of each element.
  • .parents(selector) returns all ancestors, optionally filtered.
  • .closest(selector) starts with the element itself and goes up until it finds the first match. It returns at most one element per starting element, which makes it the most useful upward method.
  • .parentsUntil(selector) returns ancestors up to, but not including, a match.

Moving down and sideways

  • .children(selector) looks only one level down.
  • .find(selector) searches every level of descendants.
  • .siblings(), .next(), .prev(), .nextAll() and .prevAll() move among elements that share the same parent.
// FAQ accordion: works for any number of questions
$('.faq').on('click', '.faq-question', function () {
  const $item = $(this).closest('.faq-item');

  $item.find('.faq-answer').slideToggle(200);
  $item.toggleClass('open');

  $item.siblings('.open')
    .removeClass('open')
    .find('.faq-answer').slideUp(200);
});

// Filtering an existing set
$('table tr').filter(':nth-child(even)').addClass('striped');
$('.card').eq(0).addClass('featured');      // first card
$('.card').not('.sold-out').first().focus();

// end() returns to the previous set in a chain
$('#menu')
  .find('a.active').addClass('highlight')
  .end()
  .addClass('ready');

Narrowing a selection with filters

Some traversal methods do not move through the tree but reduce the current set. .filter(selector) keeps matching elements, .not(selector) removes them, .eq(index) picks one by position (negative numbers count from the end), and .first() and .last() do what their names say. .has(selector) keeps elements that contain a match. Use .is(selector) when you just want a true or false answer.

Chaining and end()

Each traversal method returns a new jQuery object, so you can chain them. jQuery remembers the previous set in the chain, and .end() steps back to it. In the menu example, the chain moves down to active links, styles them, then returns to #menu to add another class. Indent such chains carefully, or split them into named variables, so they stay readable.

Confusing find with children, or parent with closest

A frequent source of "nothing happens" bugs is using .children() when the target is nested two levels deep. It only checks direct children, so it returns an empty set, and jQuery silently does nothing with it. Use .find() for deeper searches.

The upward version of the same mistake is chaining .parent().parent() to reach a container. It breaks the moment someone wraps the button in an extra div. .closest('.faq-item') keeps working regardless of how deep the button sits.

When in doubt, check .length on the result. A length of zero tells you the traversal found nothing.

Traversing can also be slower than a direct selector on very large pages, so cache results you reuse in a variable, for example const $item = $(this).closest('.faq-item'), instead of repeating the same walk several times in one handler.

Key points

Start from a known element such as $(this), use closest to go up to the component, find to go down inside it, and siblings to reach its neighbours.

Ready to master real-world web development?

Learn HTML, CSS3, Bootstrap and JavaScript hands-on with mentor-led sessions.

Explore Course