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

Profile Card using Flexbox

Nayana Bhat M•90
@nayanabhatm
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi there!,

  1. If I don’t specify the height in px, top: X% with relative position doesn’t work. Is there any way I can specify height in % instead of hardcoding the value?
  2. I have specified overflow: hidden but can still see the scrollbars when I resize the window.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Om Kakatkar•90
    @OmKakatkar
    Posted almost 4 years ago

    Hi,

    Solution for Question 1 :

    • Make sure you fix the 2nd problem first.
    • Remove margin and width in the body tag if any
    • Add the following to the div with class name "main"
        max-width: 1000px; 
        width: 40%;  
        margin: 3rem auto; 
    

    Solution for Question 2:

    • The body seems to have overflow: hidden; attached to it. Remove it.
    • Remove the margin: 5% in body as this is causing an overflow. The total width is getting calculated to 110% on x and y axes.
    • Once these 2 properties are removed from the body, the overflow still persists. This is due to the background images (top and bottom svg images) you have added in your card component. Instead of the img tag in html, you can set those images using CSS as follows:
     body {
      background-image: url(../images/bg-pattern-top.svg),
        url(../images/bg-pattern-bottom.svg);
      background-repeat: no-repeat;
      background-position: right 50vw bottom 50vh, left 50vw top 50vh;
      background-color: var(--cyan);
     }
    

    This will mostly solve your overflow issue

    If you still don't understand, try to go through MY SOLUTION

    PS : Just a heads up, use landmark tags instead of div everywhere. A quick start would be to convert the div with class "main" to a main tag instead

    Happy Coding!!✨✨

    Marked as helpful
  • Fidel Lim•2,775
    @fidellim
    Posted almost 4 years ago

    Hi Nayana, I believe the reason why scrollbars appear is that you are setting margins on your body tag :

    @media screen and (min-width: 1000px)
    body {
        /* margin: 20% 30%; */
    }
    

    With this, the whole page will really expand.

    Marked as helpful
  • SHAHAB MALIK•345
    @Shahab-Malikk
    Posted almost 4 years ago

    Hi @Nayana great work implemented things well there is no issue in website

    Keep Coding

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