Personal-Website | ‍️Create your personal website and blog with Github | Blog library

the root of your problem is that you have hardcoded the widths of some elements.

On mobile screens these elements are wider than the viewport or screen width, so come content extends off the right-hand side of the screen. This leads to the problem you describe as well as other issues.

This is also the reason why the problem got worse when you added the viewport meta tag

Some of the elements I noticed that have hard-coded widths that cause a problem are

background_color property from gatsby-plugin-manifest stands for PWA (Progressive Web Apps) features, not for the main background-color CSS property.

To change the styling for any component or element, just add a CSS/SCSS, JS, modules, etc:

setuptools, pip and wheel are a part of python package and come preinstalled. Just keep them updated to the latest version.

Firstly ditch the column constructs inside the bootstrap navbar. It was never intended for .row and .col- usage.

Because your .navbar-brand content is oversized for the S9 or any mobile device, it breaks the bootstrap mobile nav. Bootstrap 3 does not account for such oversized brand content. This is why flex is awesome in bootstrap 4.

Anyway with a few css tweeks (hacks) we can get the .navbar-brand content to break onto the next line, rather than the .navbar-toggle icon going to the next line.

See responsive example here... https://jsfiddle.net/joshmoto/k8c9uj7q/

I had a similar issue when trying to implement it.

I use Chrome by default and it was not working. When I tested it in Firefox, it did work. That made me think it was a browser problem.

After digging in a bit more, I found out the "problem" for my case. It might be the same probably for many others.

It turns out Chrome is more impatient than Firefox when loading images tagged as lazy. That means it loads the images much earlier, so an image will not be loaded when it appears at the screen but earlier than that. Firefox, on the other side, is loading the images almost when they are about to be shown at the screen.

The images I was testing were below the fold, but the page was not very long, so Chrome was loading the images anyway.

When I tried it in a much longer article, the images that were deep down the article did load lazily in Chrome as well.

Hope this helps!

The command

Your CSS syntax is wrong: don't put a space between input and [type="Submit"].

Here is your code:

I saw something similar using Ubuntu WSL. I'd been following the Jekyll WSL instructions and got stuck. There was a nice hint on Dave Rupert's blog (link) that recommended the following and unblocked me: apt install zlibc zlib1g-dev libxml2 libxml2-dev libxslt1.1 libxslt1-dev

Here's a dump of my bash history for the session:

Problem was solved by including my "core" application in the settings file in INSTALLED_APPS. Slight oversight from my part when reading the docs.

Source: Documentation - How Django discovers translations, second bulletpoint.