Something in the theme is trying to find @2x
resources when on a high DPI screen (they have @2x
appended to their name).
Apparently I've never had the Inspector Console open while browsing the website with my MacBook undocked (my desk monitors are only 1080p). With the Retina screen resolution, the scripts on the site are searching for higher res versions of all the assets, which mostly don't exist.
This amounts to a large amount of script errors, depending on the page (themes, lol).
For some reason, this is also breaking the new Javascript I wrote for the Docs. I don't know enough about Javascript to know what's going on. My guess is it's just stopping execution before it gets that far or something.
Nothing on the live site seems to break from this though, it's just a lot of 404-ing and JS console errors. It could have some consequence I'm not seeing yet though.
I don't really see us supporting High-DPI assets on the current theme (since, it needs to be replaced with a Pico solution at some point anyway). My recommendation is that I should just track down the script that's trying to replace the assets and remove it for now.
(Edit: In /style/js/scripts.js
, at the very start of the file is a section titled RETINA.JS
which seems to be our culprit.)
Thoughts?