Thanks for the info...but the plot thickens. So it seems the reason the pre-loader wasn't loading at all was because it was looking for the correct image in the wrong directory. This seems odd as I set the image directory in export to be identical to the relative-positioning of the directories on the server. To be both as specific and non-specific as possible if my sample website is located at server/directory1/directory2/page and the pre-loader image is located at server/images/constructImages/preloader.png, I am exporting the images directory as ../../images/constructImages. I am also uploading the preloader.png file to the server in that location. Yet, if I open the minified Javascript and do a search for preloader.png, I find that the Javascript thinks the image is in the root directory of the project. Naturally, Chrome's error catcher caught a 404 on the fact that server/directory1/directory2/preloader.png can't be found. But why would the minified Javascript completely ignore where I tell it the images for my "Main" sheet are to be found?
In case it matters, the specific error mentioned by Chrome when the new sheet does not load and has to be refreshed in order to appear is: Uncaught InvalidStateError: Failed to execute 'drawImage' on 'CanvasRenderingContext2D': The HTMLImageElement provided is in the 'broken' state. I suspect this is caused by the 404 from looking for the image in the wrong directory.