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

qr code with flexbox

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

Solution retrospective


how do you limit paragraphs character width

the picture is buggy or something. i can see the picture in live server but wont show up when i run the html file

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dre•610
    @hadreemustaffa
    Posted over 1 year ago

    Hi @SeenDGK.

    For the QR image, you are missing a dot before the " / " in the image src.

    Like so: <img src="./image-qr-code250x250.png" alt="">

    For <link rel="shortcut icon" href="./images/favicon-32x32.png" type="image/x-icon">.

    This image does not exist in your repo. If you choose to include it in, you can either:

    • create a folder called "images" where your HTML is, and add the icon there.
    • or put the icon where the HTML is, and change to href="./favicon-32x32.png"

    I hope this is helpful.

  • mohammed bentalb•300
    @MohammedBentalb
    Posted over 1 year ago

    consider using ch or target your width using a container width or maybe check the usage of clamp() (CSS ) (it's a cool property)

  • Mikail Ghali Imam•200
    @Imammika
    Posted over 1 year ago

    Hello there. I checked your code. I saw that you are targeting the image from a folder and if you removed the picture from the folder when you are uploading it to GitHub it will not show up on your site so you need to copy upload plus the folder you are targeting. Or you could just remove the picture from the folder and target it directly which means that you don't have to upload the folder when you are copying the files in GitHub

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub