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

QR Code

Barney•410
@waikoo
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 a small problem I'd like to ask your help with, because it seems like it happens on all the projects I'm working on. The development server's view that I get is not the same as when I make a live GitHub Page out of my solution. So I have to tinker around with the width.

Details: Leaving the card's width at 375px didn't make the text break like the way it is in the design. Changing it to 321px broke it correctly. However when I enabled the live page on GitHub, it was too narrow. Disabling the live page, changing the width to 350px, re-enabling the live page fixed the issue.

But how can it be that from VSCode's live server I'm getting a different view for the same width as compared with the GitHub Page? I used Brave to check the live GitHub Page and Chrome as the live server.

I also noticed that some of my uploaded designs look different when on GitHub as opposed to how I'm seeing it while developing. Do I really have to disable live page, make the adjustment blindly, enable it again, and see if it's like the design, or is there a better way around this? Should I use something like Vercel or Netlify instead of GitHub? Did you encounter this issue yourself?

Why could this be?

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Elaine•11,360
    @elaineleung
    Posted about 3 years ago

    Hi Barney, I use GitHub pages as well, and I don't believe I have that issue as my uploaded designs usually are quite close to the original one. Have you tried using a CSS reset yet? There can be default settings and styles in each browser that's could be giving slightly different results. I normally use Andy Bell's CSS reset code, or you can also check out some of my projects in my repo; you should be able to see the CSS and then copy the code.

    Hope this helps, and good luck!

    Marked as helpful
  • Bhaskar Bordoloi•140
    @bhaskrr
    Posted about 3 years ago

    I also used to have the same issue .Vercel solved it.

    Marked as helpful
  • Mihirkumar hitendrabhai nayak•180
    @mihir2226
    Posted about 3 years ago

    just use the chrome inspect tool and do changes through it. if you are not comfortable with the live server. after you satisfy with the changes copy them and paste them into your code.

    it kind of works for me every time when I stuck. hope it will work for you too.

    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

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