Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial![](https://ecs-static.teamtreehouse.com/assets/views/marketing/shared/community-banner-white-47072046c51352fe6a69f5e691ff5700b28bb11d45197d7bdf066d9ea3f72d0c.webp)
![Michael Williams](https://uploads.teamtreehouse.com/production/profile-photos/9059642/micro_photo-1544943910-4c1dc44aab44.jpg)
Michael Williams
Courses Plus Student 8,059 PointsWhy did the button move in between the spoilers when clicked? Treasure didn't explain why, only how to fix it.
In this video — https://teamtreehouse.com/library/what-is-traversal — about DOM traversal, there are two spoilers hidden with their own buttons. When you click the button, it's supposed to reveal it's corresponding spoiler. However, when Treasure clicked on the button, both disappeared and a button appeared in between the spoilers. She showed how to fix it using traversal, but didn't explain why it wasn't functioning properly. Can anyone explain why? Thanks!
1 Answer
![handy christian](https://secure.gravatar.com/avatar/d2fc1ea50ce1b040215ee8a7bbbfa98f?s=96&d=https%3A%2F%2Fecs-static.teamtreehouse.com%2Fassets%2Fcontent%2Fdefault_avatar-445fbbabfc8dc9188fb5967fe43322ee0c3e0dd1e10f378bf8343784af5a13eb.webp&r=pg)
handy christian
2,899 PointsIt was because the function says: when we click the event (the button that we click) all the span will reveal, while the other button we didn't click still shown and reveal between or under the spoiler. That's why we better use $(event.target).prev() or $(event.target).next() rather than $('.spoiler').show() because it will not show all of the span.
Let me know your opinion about this :D