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

Responsive block with CSS Grid

barbarian10•10
@barbarian10
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Why does the div overflow the border on different devices (e.g., iPhone 12 Pro)? How to fix it? Why does the third div (why) appear smaller in width than the second (subscription) on iPhone 12 Pro? How to fix it?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kaylo•270
    @KayloPortal
    Posted about 2 years ago

    🎊Hello! Nice job

    • I don't understand your first question, but for the second question, I hope I can provide a good solution.

    • In the .grid class, a width of 240px is set for each column. This means that each column should be at least 240px wide. It is obvious that in devices with a width of less than 480px, such as the iPhone 12, it becomes smaller due to the lack of enough space.

    🎄How to fix the problem:

    1/ Using media query and rem:

    • The size of the rem unit is based on the font size in the <html> tag. By default this size is 16px.

    • According to this case, rem size can be changed by using media query in different view port sizes

    • for example : @media (max-width: 1440px){ html { font-size: 16px; } }

    This piece of code sets the size of the html font-size to 16px, on devices with a width of 1440px and less. you can use a rem unit and change it for different viewports, instead of using fixed points like px.

    2/ Using media query and grid

    • Since the ratio of the mobile is different from the desktop, it is obvious that the arrangement of the elements is also different in these two devices. As we can see in the designed file, due to the smaller width of mobile devices, we need to change our Grid design from a two-row and two-column design to a three-row and one-column design in a viewport width of less than 800 pixels.

    • Also, there more different ways to fix these type of problem and make the elements more responsive, like setting fr or ch width on elements, or using clamp(), min() & max().

    • You can google "Responsive Layouts" & "rem & em units" to get more information about it

    • I hope it was useful✨

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