Website title and navigation links alignment bug about pixyll

[johno]

Yeah, I've seen the same behavior, and have been looking into it. No luck thus far, but I will keep you posted.

[bandali0]

Yeah I couldn't figure out why either, but thanks and do let me know if you find out anything.

[anandrajaram]

fwiw, I "hacked" this for desktop and tablet media screen types

 .site-header .site-nav {
    margin-top: -2.5rem;
  }

and it shows up like this:

[johno]

It's quite strange because I was able to get pixyll.com to exhibit that behavior around every 10 page loads. However, now, it doesn't seem to be occurring.

I'm going to try:

.site-nav {
  margin: 0;
  padding: 0;
}

Perhaps it will help resolve the problem.

[bandali0]

@anandrajaram @johnotander I'm afraid none of those helped fix the problem.

A temporary solution I've found to work is giving a float: left; to the title a tag, but the problem with that is the rest of the page is shifted up a bit, along with the navigation links (different than when you refresh the page). But anyhow, maybe we could float left the title and then push things down again?

Also, this happens in chrome on Windows as well, but not on Firefox.

[johno]

Thanks for looking into it @aminb.

I will add float:left; to the site title tag and float:right; in the site-nav with a clearfix below them. Then readjust any necessary whitespace to match it to what's existing. I should get to this later this afternoon.

[bandali0]

@johnotander You're welcome and I hope it helps and actually works out as a solution. Looking forward to the commits.

One other thing I've realized is that for this bug to happen, you have to open the page from url bar (clicking the link from other pages doesn't reproduce) and sometimes you have to close (end) the incognito session and then go incognito again for the bug to show up, in case you're trying with incognito mode as well.

[johno]

@aminb @anandrajaram Looks like this should fix it. Let me know if you can still reproduce the behavior. Thanks!

[bandali0]

@johnotander Seems like it's been fixed. Fantastic!