Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

Todo app

Duyen Nguyen•950
@Duyen-codes
A solution to the Todo app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I'm stuck with deleting item from the list. Could you please help give me some hints on this please. I'm still a beginner but wanna challenge myself with this. Thanks for your help!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Matthias•630
    @astragenius
    Posted over 3 years ago

    Hey your bg-images and icons dont load correctly.

    Remove "/" on all your img url path.

    for example:

    body {
        --bg-img: url("/images/bg-mobile-dark.jpg");
    }
    
    to
    
    body {
    
        --bg-img: url("images/bg-mobile-dark.jpg");
    }
    
    

    do this on all your image urls. After this all images should load correctly.

    Marked as helpful
  • Progress Aienobe•565
    @Paienobe
    Posted over 3 years ago

    To do the deleting, you could push all the items added to the list to an array and then when you want to delete something, you can use filter method and return only the items not equal to the item you want to delete. Hope this helps

    Marked as helpful
  • imNotAli•230
    @AliNaderii
    Posted over 3 years ago

    Hey there :) Well, I tested your code and this is what I found.

    • Your querySelectorAll is not working as it should and when I used getElementsByTagName it worked properly.
    • The way that you are using spread syntax is not needed, querySelectorAll returns an array by default.
    • What you are pushing to todoItems is not necessary, you could just use querySelectorAll.
    • I think it's better to use createElement and then appendChild instead of insertAdjacentHTML.

    I hope you find it helpful :)

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub