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

Results summary component (responsive) + hover transitions

kmigel•40
@kmigel
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I don't really understand how to position the items in the summary section (how to make the 80/100 stick to the right etc.) so I solved it by using position relative but that created some problems when I was making this component responsive.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    aaronrubinstein•480
    @aaronrubinstein
    Posted over 2 years ago

    Hey Kmigel,

    A trick to making a flex item "stick to the right" is to use margin-left: auto. That causes the item's left margin to expand to take up as much free space as possible, which pushes it all the way to the right.

    Taking a quick look at your code, here are a few suggestions:

    • Wrap your-points and max-points in a new div (making them a single flex item within the summary-item container) and style that div with margin-left: auto
    • You should be able to remove justify-content: center from summary-item (you want the flex items to be justified left, except for the last one that you push to the right)
    • Remove the absolute and relative positioning on all the items within the summary-item container. You shouldn't need that.

    That should address the responsive issues. Hope that helps 👍

    (here's my code for the summary item if you want to take a closer look at the css)

    Aaron

    Marked as 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

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