You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Hey- I am having two small bugs for my league's website. When click on matchups, the screen freezes. If I hit refresh, it will load the matchups just fine. Also, when I click on standings, I get a loading symbol. That problem doesn't get fixed when I hit refresh
Click on matchups or league info and then standings
See error
Expected behavior
I expected matchups to load immediately when I clicked on matchups.
When I clicked on league info and then standings, I expected to see league standings.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: [e.g. iOS] OS Big Sur
Browser [e.g. chrome, safari] Safari
Version [e.g. 22] 14
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
Hey- I am having two small bugs for my league's website. When click on matchups, the screen freezes. If I hit refresh, it will load the matchups just fine. Also, when I click on standings, I get a loading symbol. That problem doesn't get fixed when I hit refresh
Your League ID
My website is: www.leagueofmisfitboys.com
Our ID is: 654056594040029184
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expected matchups to load immediately when I clicked on matchups.
When I clicked on league info and then standings, I expected to see league standings.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: