Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 12 months ago

blog - preview -card ->solved

ritu jha•60
@ritujha19
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What specific areas of your project would you like help with?

I have a question --> why does my file looks different in edge and different in google chrome .

in edge my files looks prefect but in chrome my files looks different its like look everything goes up .

why does it happens ?

i don't know it happens on only laptop or anyone else also so please, preview my solution if you see this so. Please give me feedback .

OR

if u know why its happened , then please let me know about this also and also u know how to resolved it , so please help me also to resolved it .

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • khannfouad•230
    @khannfouad
    Posted 12 months ago

    The issue is most likely coming from the 70vh you've set on the container. Different browser's view ports react in different ways when vh is concerned. Also it's a funky property that's why I like to avoid it.

    Solution will be to add a max-width property. Use 100vh on the body to center the container div. and remove height altogether from the container. Let your margin and padding handle the vertical length.

    Marked as helpful
  • Omprakash Rahangdale•900
    @OmprakashR
    Posted 12 months ago

    Hi @ritujha19,

    Great job on your project! I have a few observations for your code that might help improve it:

    Add min-height: 100vh to the body to center the div. Remove the vh value and replace it with px values. Set the height to auto, and use max-height and min-height properties as needed. Additionally, remove the top margin. Hope this helps!

    Thank you!!

    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
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 1st-party linked stylesheets, and styles within <style> tags.

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.

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