Addon info is severely broken on Snap! v12 #58

Closed

opened 2026-06-04 13:33:00 -05:00 by PPPDUD · 3 comments

PPPDUD commented

2026-06-04 13:33:00 -05:00

(Migrated from github.com)

Whenever you try to open an addon's information in Sparkle on Snap! v12, the entire site freezes and the console shows Uncaught TypeError: world.add is not a function followed by hundreds of identical Uncaught TypeError: Cannot read properties of null (reading 'keyboardFocus') messages, as well as a sprinkling of Uncaught RangeError: Maximum call stack size exceeded. (Pictured below is the state of the site when it freezes.)

@Alessandrito123 I believe that this is related to Morphic because the files where these errors are coming from are morphic.js and widgets.js. Would you please see if you can get this fixed?

Whenever you try to open an addon's information in Sparkle on Snap! v12, the entire site freezes and the console shows `Uncaught TypeError: world.add is not a function` followed by hundreds of identical `Uncaught TypeError: Cannot read properties of null (reading 'keyboardFocus')` messages, as well as a sprinkling of `Uncaught RangeError: Maximum call stack size exceeded`. (Pictured below is the state of the site when it freezes.) <img width="759" height="553" alt="Image" src="https://github.com/user-attachments/assets/9caca4c2-432a-4ff3-8aa9-9ef66bb1ef64" /> @Alessandrito123 I believe that this is related to Morphic because the files where these errors are coming from are `morphic.js` and `widgets.js`. Would you please see if you can get this fixed?

PPPDUD commented

2026-06-04 14:59:30 -05:00

(Migrated from github.com)

Nevermind, it was a bug caused by a faulty change that I had made to my local copy of Sparkle.

😕 1

codingisfun2831t commented

2026-06-11 20:07:48 -05:00

(Migrated from github.com)

What was the change?

PPPDUD commented

2026-06-12 10:38:25 -05:00

(Migrated from github.com)

What was the change?

It was an early version of #60 where I accidentally used a comma in place of a plus sign, causing the bizarre symptoms described in the issue's description.

> What was the change? It was an early version of #60 where I accidentally used a comma in place of a plus sign, causing the bizarre symptoms described in the issue's description.

Commenting is not possible because the repository is archived.