Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 4 years ago

Order Summary Component Challenge builded with basic HTML and CSS

murilo•110
@mlzzi
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hy guys,

I completed the challenge and all seem to work properly, but not the background. I can't center the background and if the screen is bigger than 1440px a white strip appear on the left side. Another issue is that I'm not sure if the desktop version is responsible. In the devtool of chrome, looks responsible. But in the normal window if I resize the screen it doesn't work.

Thanks

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted almost 4 years ago

    Hey, awesome work on this one. Layout in general is fine. About your query, let's try to fix that.

    • What you only need is the size of that background image. Try using background-size: contain that should fix it.
    • On making it responsive, to be honest, I was confused on how did this work. Remove the width property on the body. I was like "oh, how did it fix that" hahahah.

    Some other suggestions would be:

    • The imgon the card should have used alt="", since it is just a vector image. When an image only acts as a decoration, better use alt="" on them, if the image adds content to the website, use a descriptive alt value. Also, avoid including words that relates to "graphic" like "picture, drawing, icon, logo" as a value in the alt attribute. Assistive tech will handle those for you.
    • The music-icon should use alt="" as well, it is just decoration.
    • The change should be a link a tag, not p. An interactive element should use an interactive html element. p tag alone is not interactive, well I am talking about having focus.
    • proceed to payment and cancel order should use a tags as well.

    Other than those, it looks good. Great work.

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