Chrome seems to be more strict when it comes to loading scripts than other browsers. It seems we're sending /opac-tmpl/bootstrap/lib/enquire.min.js and /opac-tmpl/bootstrap/js/script.js with a MIME type of text/plain when we should be sending it with type application/javascript. This causes warnings when running under https and the following error message to appear in the console: 'Resource interpreted as script but transferred with MIME type text/plain.' This relevant code is inside a modernizr block so I'm not sure how to proceed with a fix.
Not that this is the best solution, but perhaps adding: AddType text/javascript .js in the appropriate apache configuration files would work? (http://stackoverflow.com/questions/3467404/chrome-says-resource-interpreted-as-script-but-transferred-with-mime-type-text) I haven't tried it.
I could recreate the error messages in the Chromium console on my local dev install, which is not using https. No sign of any warnings in Firefox, though.
Is this bug still valid? I don't see any errors when I look at our OPAC in Chrome.