Starter Pages do not appear to be loading correctly

boborchard commented 4 years ago

Description

When visiting the starters on https://gatsbyjs.org, it appears that some of them are not loading correctly in a Brave browser

Steps to reproduce

Open a browser window and visit the starters page https://www.gatsbyjs.org/starters
Randomly select a starter and open the starter's page
Sometimes you'll need to do a hard refresh to get it to load, but on some browsers that doesn't show the correct layout (like on Brave).
It does not appear to matter which starter you look at, but it does seem to be random. A few I've experienced this issue on are https://www.gatsbyjs.org/starters/seabeams/gatsby-starter-auth-aws-amplify/ and https://www.gatsbyjs.org/starters/service-relief/gatsby-starter-service-relief/

I've observed this on Chrome and Brave (as well as in incognito/private for each) so far.

Expected result

The page should load entirely, showing the header and correct page styles.

Actual result

The page flashed, showing the header and styles initially, but then showed the main body of the page without a header/footer.

Recording: https://share.getcloudapp.com/GGuNgobJ

Screenshot:

smkamranqadri commented 4 years ago

Not able to reproduce.

laneparton commented 4 years ago

Are you able to reproduce the issue without an ad blocker on Chrome (such as an incognito window)? Does your ad blocker say anything interesting in its log of loading the page?

smkamranqadri commented 4 years ago

I checked on brave, not.chrome.

boborchard commented 4 years ago

@laneparton I checked in Incognito without any extensions in Chrome and Brave when I encountered this.

AhsanAyaz commented 4 years ago

What chrome version do you have at the moment @boborchard . I'm not able to reproduce this as well :(

boborchard commented 4 years ago

I'm currently using v80.0.3987.149

smkamranqadri commented 4 years ago

@boborchard I am using the same version of Chrome, here is the video.

https://recordit.co/bpGvkpGNyE

github-actions[bot] commented 4 years ago

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open! As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

github-actions[bot] commented 4 years ago

Hey again!

It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else. As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks again for being part of the Gatsby community! 💪💜

gatsbyjs / gatsby