Closed aisejohan closed 5 months ago
And what do you know... all of a sudden it's working... so maybe it is the server serving the js file doing weird stuff?
I am going to reopen this because it happens frequently on various devices
Also on firefox. Inspection gives the error None of the “sha384” hashes in the integrity attribute match the content of the subresource. The computed hash is “7jzYCmSCwaYsfVg4nDTWjFA+Ldb317135sF3guZkTfA8HfqDX3ectSa4fb1sO1v4”.
and the error Uncaught TypeError: $(...).bonsai is not a function
OK, I tried to fix this hashes problem and it sort of worked... On the server, I changed all the downloads of the jquery-bonsai files to the minified versions and to version 2.1.3. Unfortunately, I think the hashes are not stable for the minified versions (even during my short time working on this the file https://cdn.jsdelivr.net/npm/jquery-bonsai@2.1.3/jquery.bonsai.min.js
changed.. because of different minifications one using Terser v5.19.2 and one using UglifyJS v3.3.20 .... see also this page at jsdeliver.) I will monitor and if the problem reoccurs, then I will go with the non-minified ones (these are really not much bigger).
OK, I went with the non minified ones. see: integrity.txt
On chrome (and not on firefox). Happens on the table of contents and on the parts and chapter pages and on results of searches. Using inspect in chrome complains about the hash/integrity mismatch and about $(...).bonsai not being a function.
I've had this problem intermittently with different versions of the chrome browser, so I decided to make a bug report, but likely this bothers noone except me.