Alle rapporter
lovelinks_displayed rapporterer
#152035: "Game doesn't load on older Chromium browser - not sure if necessary"
fixed: Bug er blevet fixet
1
Hvad handler denne rapport om?
Hvad skete der? Vær venlig og vælg nedenunder
På et tidspunkt kunne jeg ikke få adgang til spilsidens funktioner
Detaljeret beskrivelse
• Hvad blev der vist på skærmen, da du blev blokeret (Blank skærm? Noget af spilbrugerfladen? Fejlmeddelelse?)
I happened to try opening the game under an older Chromium-based (Brave) desktop browser (Chromium v103.0) on an old El Capitan macOS that I also use for BGA at times. It's fine on up to date Brave with newer macOS, and mobile Safari for me.
I don't know that it is important to bother supporting older environments, but figured it was worth sharing at least as an FYI in case it exposes any weird edge cases you may feel need a look.
I see the following in the console and the game loading page with the game box image stops at 10% every time, only in this old environment.
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'match')
at e.setRotate (lovelinks.js:1:14739)
at e.updateDisplay (lovelinks.js:1:12797)
at e.registerLink (lovelinks.js:1:9278)
at e.appendLink (lovelinks.js:1:11367)
at t.setup (lovelinks.js:1:27165)
at t.completesetup (ly_studio.js:1:498947)
at lovelinks?table=609626492:2082:28• Hvilken browser bruger du?
Google Chrome v103
Rapporthistorik
5. jan 2025 15:46 •
Swinkels • Bug er blevet fixet:
13. jan 2025 19:46 • I added a case for when `dojo.getStyle(element, 'rotate')` returns undefined. Which seems to be the case in your browser. It should be fixed now.
lefalaf • Bug er blevet fixet:
13. jan 2025 21:15 • Thanks! I can confirm that it is fixed. The game loads now in that environment.
lefalaf • Bug er blevet fixet:
14. jan 2025 0:45 • My turn came back around and there were no issues playing on the older environment. Looks good.
Tilføj noget til denne rapport
Vær sød at tilføje, det du finder relevant for at vi kan løse fejlen i spillet eller forstå dit forslag:
- Et andet bord-ID / træk ID
- Løste F5 problemet?
- Skete problemet flere gange? Hver gang? Tilfældigt?
- Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.