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

Simple QR-Code page

Haarith•150
@HaarithBinSabur
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Please leave a comment on the code I used and what I should have used instead or what I could have used instead. I actually did this one a few days ago but I revamped it after seeing Kevin Powel using CSS variables, it looks and feels way easier to use compared to writing every color out. Please feel free to review my code and send back feedback

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • gfunk77•1,270
    @gfunk77
    Posted almost 2 years ago

    Haarith, Nice work on the qr code card. Looking at your css, I would suggest removing all the selectors that you don't actually need. For example, you could do * { margin: 0, box-sizing: border-box } and eliminate the ::before and ::after. Keep img { display: block; width: 100% } but you can remove the rest. You can delete all of these because you are not actually using them and they won't have any impact on your code ->

    1. Remove built-in form typography styles / input, button, textarea, select { font: inherit; } /
    2. Avoid text overflows / p, h1, h2, h3, h4, h5, h6 { overflow-wrap: break-word; } /
    3. Create a root stacking context / #root, #__next { isolation: isolate; } / the actuall html page height*/

    html{ height: 100%; }

    I think your css would look a lot cleaner with only the essentials needed for your component. Your :root variables look good! Well done!

    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