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

Responsive Order Summary Component

Noemi Gali•280
@NomiDomi
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


As always, would greatly appreciate any feedback.

Also, how do you guys center vertically when you have .main-container { position: absolute }

I was able to center horizontally because I had a set width for the container, but my height was auto.

Tried display flex and align-items but it didn't work.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ben Andrew Merritt•345
    @b-a-merritt
    Posted over 3 years ago

    Hey!

    I think your intuition to use flex-box is spot on, but it of course cannot be used with a position: absolute item. (An absolute-positioned item is removed from the flow, and flex-box items need to be in the flow).

    One way you could accomplish this is to put your main-container div in another container, position that container absolute with a set height of 100vh and a width of 100vw, then use flex-box on the main-container inside of the new container.

    Whew! That seems to me like too much work.

    What might be better is if you used the "background-image" CSS property on main rather than displaying an HTML <img/> element. This way, you could just immediately set main to 100vh and 100vw while positioning main-container with flex-box right away.

    I think you did not do this because you wanted to display two different images - one for mobile and one for desktop. Sorry for explaining this if you already knew it, but you can use a media query to display a different image at a different screen with by using the following code in your stylesheet:

    
    main {
      background-image: url('RELATIVE_PATH_FOR_MOBILE_HERE');
    }
    
    @media only screen and (min-width: WIDTH_AT_WHICH_YOU_WANT_TO_CHANGE_HERE) {
      background-image: url('RELATIVE_PATH_FOR_DESKTOP_HERE');
    }
    
    

    If that wasn't the reason or that's not helpful, I'd be interested to know!

    Happy coding!

    Marked as helpful
  • Anthony Rosman•510
    @D3press3dd
    Posted over 3 years ago

    I like the shadow in the plan part, really cools, btw where did you learn css?, i want to learn the :root part and the variables that you declared, i was looking in udemy bussines account but i couldnt find a good css course updated :c hope you have a great day and happy coding💻

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