Semanticmediawiki: Tippy.js not always firing

[D-Groenewegen]

Setup and configuration

• SMW version: 3.1.6
• MW version: 1.31.1
• PHP version: 7.2.31
• MariaDB: 10.1.44-MariaDB-0+deb9u1
• Chameleon: 2.3.0

Ever since qTip was replaced with tippy.js, in early 2019 I think, I'm having the problem that the tooltips don't render 5% of the time, often but not necessarily after saving a page. There's no javascript conflict reported in the browser console, but the console does not show a GET request for the relevant tippy module (I can see two, apparently identical requests for ext.smw.tooltip but not ext.libs.tippy).

[kghbln]

Perhaps relateded to:

Source-Map-Fehler: Error: JSON.parse: unexpected character at line 2 column 1 of the JSON data
Ressourcen-Adresse: https://sandbox.semantic-mediawiki.org/w/extensions/SemanticMediaWiki/res/libs/tippy/popper.min.js?74d0b
Source-Map-Adresse: popper.min.js.map

and

Source-Map-Fehler: Error: JSON.parse: unexpected character at line 2 column 1 of the JSON data
Ressourcen-Adresse: https://sandbox.semantic-mediawiki.org/w/extensions/SemanticMediaWiki/res/libs/tippy/tippy.js?e5280
Source-Map-Adresse: index.js.map

See Source map errors

Not sure though which version of tippy.js is used by SMW. However since it was introduced there were some new upstream releases.

[D-Groenewegen]

Thanks for the hint: you could well be on to something. @krabina reported identical or similar source map errors in relation to another problem, one that I happen to share:

https://github.com/SemanticMediaWiki/SemanticResultFormats/issues/568#issuecomment-601077875