Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

CSS properties for a QR-CODE component

LLL0908•40
@LLL0908
A solution to the QR code component 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 tried hard to let every items go to the right place. It's difficult for me since I'm really a beginner. I'd like to try different methods next time and make my coding structure more clearly.

What challenges did you encounter, and how did you overcome them?

I'm confused with the position and I searched for the solution.

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

Position

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • dbmourits•60
    @dbmourits
    Posted over 1 year ago

    You did a pretty good job.

    i see you used both "display: flex" and "position: absolute" i would advise to only use "position" if it is absolutely necessary. In my opinion you could remove the (position, top, left and transform in .qrcode) and try playing with padding (and margin) around objects.

    Starting with "display: flex" is good practice. https://css-tricks.com/snippets/css/a-guide-to-flexbox/

    position can be helpfull when you want to move things more independently/fixed from the rest of the code and or make objects interactive. Maybe the following website helps you a little further in your understanding about position: https://css-tricks.com/almanac/properties/p/position/

    Marked as helpful
  • P
    Boris•4,130
    @makogeboris
    Posted over 1 year ago

    Hi LLL0908, great job, here are some feedback

    • On your body element you have a typo should be display: flex not felx, I guess that's why you had to use position: absolute and transform: translate on your .qrcode to center it, you can delete those lines. Also add a min-height: 100vh, flex-direction: column on your body.
    • All content should be wrapped within landmarks. Wrap a main tag around your qrcode and a footer for the attribution.
    • Your .qrcode should have a max-width in rem not width. Try as much as possible to avoid setting fixed widths and heights on elements, use max-width or min-height if you have to.
    • Consider using a modern CSS reset at the start of the styles in every project. Like this one modern css reset.
    Marked as helpful
  • Przemysław Rajn•40
    @rzuanisko
    Posted over 1 year ago

    For me, that's realy nice work. U have good proportion, but u can add biggest margin-top on your .container.

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

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