Might be worth reaching out to the addon authors. Hard to say whether the page or the addon is at fault, but they might be interested to know it even if it’s the page’s fault.
It looks like it’s the addon’s fault, and has already been fixed in the github version. It’s also been abandoned, so it’s probably not worth keeping around anyway.
Might be worth reaching out to the addon authors. Hard to say whether the page or the addon is at fault, but they might be interested to know it even if it’s the page’s fault.
It looks like it’s the addon’s fault, and has already been fixed in the github version. It’s also been abandoned, so it’s probably not worth keeping around anyway.