All reports
lovelinks_displayed reports
#152035: "Game doesn't load on older Chromium browser - not sure if necessary"
fixed: Bug has been fixed
1
What is this report about?
What happened ? Please select from below
At some point I was unable to access the game interface
Detailed description
• What was displayed on the screen when you were blocked (Blank screen? Part of the game interface? Error message?)
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• What is your browser?
Google Chrome v103
Report history
5. Jan 2025 15:46 •
Swinkels • Bug has been fixed:
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 has been fixed:
13. Jan 2025 21:15 • Thanks! I can confirm that it is fixed. The game loads now in that environment.
lefalaf • Bug has been fixed:
14. Jan 2025 0:45 • My turn came back around and there were no issues playing on the older environment. Looks good.
Add something to this report
Please add here anything that seems relevant to reproduce this bug or understand your suggestion:
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appears several time? Everytime? Randomly?
- If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.