I get the same error about decoding font and OTS parsing even without loading an image. (It seems to be something with Figwheel's HUD.)
Also similar to @ericcervin, but using that template project and adding an image to resources, loading it in setup
like so:
{:color 0
:angle 0
:img (q/load-image "foo.png")}
changing update-state
to look like this: (defn update-state [state]
; Update sketch state by changing circle color and position.
(merge state
{:color (mod (+ (:color state) 0.7) 255)
:angle (+ (:angle state) 0.1)}))
And drawing it like so in draw-state
: (q/fill (:color state) 255 255)
(q/image (:img state) 0 0)
I get to see the image, w/o any cross-origin errors in either Chrome or Safari.So the cross-origin data error is just there all the time, and has nothing to do with my loading of an image? I can now see that if I go ahead and use the image properly then it does display, but I'm still getting the error message in the Javascript console. The cross-origin data error is just a constant, and a red herring when debugging? When my student's project wasn't working I cut everything except the load-image
, figuring that that shouldn't give me an error, but then I saw the error that led to this whole digression....
I don't see any cross-origin error.
Debugging in the browser is such a madness. I'll add that I tested on Windows 7, Firefox 66.0.3 (64-bit), and Chrome Version 73.0.3683.103 (Official Build) (64-bit)