Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 years ago

Todo app solution with FlexBox

AlexMagargiu•160
@AlexMagargiu
A solution to the Todo app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Pretty hard exercise. I also added functionality to remember user themes on reload and a + SVG when you're typing in your task.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aryan Kumar•390
    @aryanda1
    Posted about 2 years ago

    I noticed two small problems first cant add completed task second the way u implemented drag and drop is weird. Normally the draggable item will be placed the position were it was dropped rather than on some place else, And its consantly getting dropped as i move up or down, And like u saved the theme, u can also saved the todos also Now encountered third problem, when i removed all items using clear completed, now i cant add any new item, enter doesnt adds any item, but clicking the svg icon removes input value but doesnt adds it, also when in active tab, u can remove the ticked todos, and same goes for the completed tab The bottom three buttons which appear in mobile mode appear differenlty now, WHen i go from desktop to mobile and again to desktop they dont merge with the last row which contains item left and clear completed button And that Challenge by Frontend Mentor. Coded by Magargiu Alexandru Razvan. should be placed at bottom of all your content, rather than on your main content. ANd also by deleting items, why the top images starts to come down?

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 all CSS, SCSS and Less files in your repository.

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.

How does the JavaScript validation report work?

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

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

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

Log in with GitHub