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

Responsive product-list-with-cart

react, redux-toolkit, tanstack-query, typescript, pure-css
P
Nishanth Venkatesan•1,030
@nishanth1596
A solution to the Product list with cart challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I really enjoyed this challenge. Since I am accousmed to tailwind css, I faced a lot of setback in using vanilla css. But there were perks of using it, I used module css, so debugging was way to simpler compared to tailwind but I have to write a lot of code.

What specific areas of your project would you like help with?

The alignment of the "Add to Cart" button is incorrect, and I’m not sure why it’s getting wrapped. However, if I remove left: 50%, the issue is resolved. It seems to be related to positioning—since there isn’t enough space, the button is wrapping to the next line.

I've never encountered this issue before, so I’m unsure how to fix it. Any help would be greatly appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Waldemar Glaz•845
    @waldekglaz
    Posted 3 months ago

    Hi, @nishanth1596. The simplest fix is to give some fixed width to your button. width:170px works well on >768px.

    Marked as helpful
  • Marzia Jalili•7,610
    @MarziaJalili
    Posted 3 months ago

    Eid Mubarak!

    You can resolve the issue simply by putting a minimum width for the buttons. We will set it to a % value to ensure it works for any screen size. And therefore, we will need the justify-center Tailwind className to center the conent inside the button everytwhere.

    • So add the following lines:
    <button className="min-w-[80%] justify-center">
    
    • Or you can added to the ._button_18y89_1:
    min-width: 80%;
    justify-content: center;
    

    This definitely works!

    Last suggestion, instead of going back to pure CSS for elements like ._button_18y89_1 you can use the @layer and @apply nested inside it for adding those Tailwind classes.

    You can go through the documentation and understand it perfectly, it's a cake walk, pretty straight forward.

    Hope the tips were helpful!

    😎😎😎

  • P
    Nishanth Venkatesan•1,030
    @nishanth1596
    Posted 3 months ago

    Hi @MarziaJalili Could you help me with this "Add to Cart" button issue?

    I've spent a lot of time on it but couldn't fix it. So, I decided to seek your help first before proceeding any further

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

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