After running into issues in the Gitea web-based interface, the gitea devs directed me to the dom-input-range developer because they extensively use this module for text expansion, and the issue is in that dependency of this module.
Unfortunately the dev of dom-input-range is completely unresponsive (iansan5653/dom-input-range#7) so I'm opening this issue here as "one level up" to potentially fix the problem.
For a more detailed description, please see the linked issue. For a detailed analysis of WeakRef() and why our platform doesn't implement this, see e.g. https://repo.palemoon.org/MoonchildProductions/UXP/issues/1740
I'm hoping you can remove the references (no pun intended) to the WeakRef JS API so dependent upstreams don't run into these issues.
After running into issues in the Gitea web-based interface, the gitea devs directed me to the dom-input-range developer because they extensively use this module for text expansion, and the issue is in that dependency of this module.
Unfortunately the dev of dom-input-range is completely unresponsive (iansan5653/dom-input-range#7) so I'm opening this issue here as "one level up" to potentially fix the problem.
For a more detailed description, please see the linked issue. For a detailed analysis of
WeakRef()and why our platform doesn't implement this, see e.g. https://repo.palemoon.org/MoonchildProductions/UXP/issues/1740I'm hoping you can remove the references (no pun intended) to the WeakRef JS API so dependent upstreams don't run into these issues.