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

JavaScript JavaScript and the DOM (Retiring) Making Changes to the DOM Removing an Element from the DOM

Posted by Robert Crocker
Robert Crocker
3,748 Points

I think there is an issue with this question. I have tested this code in my own browser, but it isn't working here.

I would appreciate someone taking a look at this code. It seems to work in my browser, but I can't get it to work in the emulator. Thank you!

index.html 
<!DOCTYPE html>
<html>
    <head>
        <title>DOM Manipulation</title>
    </head>
    <link rel="stylesheet" href="style.css" />
    <body>
        <ul>
            <li id="first">First Item</li>
            <li id="second">Second Item</li>
            <li id="third">Third Item</li>
        </ul>
        <script src="app.js"></script>
    </body>
</html>
app.js 
let myList = document.querySelector("ul");
let firstListItem = myList.querySelector("li");
firstListItem.remove();

1 Answer

Steven Parker
Steven Parker
229,783 Points
Steven Parker
Steven Parker
229,783 Points

I love it when a question teaches me something new — I wasn't aware of that method! And yes, it does work in my browser. But apparently it's not implemented in the JavaScript engine that the challenge uses.

I don't know if the omission is intentional, but the challenge is probalby expecting you to use the "removeChild" method that was introduced in the course, instead. I know you can pass the challenge that way.

You may want to report this as a bug to Support.