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

barcode using html css

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

Solution retrospective


I have difficulty in using properties of display like inline , block etc. some one please guide me how and when we use these properties.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Daniel 🛸•44,790
    @danielmrz-dev
    Posted over 1 year ago

    Hello @asadalimcj!

    Display: Block = The element uses 100% of the parent element's width. You can set its height and width.

    Display: Inline = The element behaves like a word. You can place other elements next to it because it doesn't use 100% of the parent element's width. In this case, you can't set it's height or width.

    Display: Inline-Block = The element behaves like a word, does not use 100% of the parent element's width but you can set it's height and width.

    It's not that hard. With practice, you're gonna master it very soon.

  • P
    Øystein Håberg•13,260
    @Islandstone89
    Posted over 1 year ago

    HTML:

    • You need a <main>, this is important for accessibility. Change <div class="main"> into something like <main class="card">.

    • You don't need any divs at all in this challenge. So, I would remove them.

    • The image must have alt text. This is essential for screen readers to understand the image. The alt text should be descriptive, and in this example, it also needs to say where it leads (frontendmentor.io).

    CSS:

    • It's good practice to include a CSS Reset at the top.

    • It seems you only have font-weight of 200 included - go back to Google Fonts and select the appropriate sizes.

    • Font-size must never be in px. Use rem instead.

    • Remove the fixed height on the image. Also, remove margin-top. Add display: block, and change width: 90% to max-width: 100% - this prevents it from overflowing its container.

    • To add some space between the image and the edge of the card, use padding on the card itself.

    • Remove the fixed width and height on the card. You rarely want to set fixed dimensions, as this easily creates issues with responsiveness.

    • Add a max-width of around 20rem on the card - this is so the card doesn't get too big on larger screens.

    • Remove the fixed height (see a pattern?) on the heading and the paragraph.

    • A more efficient way to center the card horizontally and vertically is to use Flexbox on the body:

    display: flex;
    flex-direction: column;
    justify-content: center;
    align-items: center;
    min-height: 100vh;
    
    • After you have done this, remove the margin-top and margin-bottom on the card.

    • Remove display: inline-block on the card. inline-block is mostly used for elements like buttons.

    Hope this has been clear and helpful - best of luck :)

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