Closed Carifio24 closed 2 years ago
As discussed over Zoom, we now think this is just that a new release of the webclient needs to be made. The testing_webclient
version doesn't display this issue.
I just pushed through a webclient release and this indeed seems to be fixed now.
I noticed this issue while trying to load my test HiPS slice in the webclient (previously I had been using the research app). Despite loading in
pako
anduuid
before the engine (see #349), I'm seeing the following two errors when I load up the web client:The
import
statements that the errors are referencing shouldn't even trigger ifpako
anduuid
are present already, which they should be here (as we're pulling them in via script tags). Forpako
, this error doesn't actually seem to matter - I can save a tour just fine (andpako
is present in the browser'sWindow
object). Foruuid
, however, this isn't the case - loading a HiPS catalog doesn't work, anduuid
isn't defined in the window (which it should be).However, I can't reproduce this locally - when I run the web client from my machine, everything works fine. Based on the errors, could there be some CORS setting on the web client that's causing an issue with the script imports?
As for why this only ends up affecting
uuid
, the only lead I have is from the minified JS inwwtsdk.min.js
. After some pretty-printing, the minified JS for the imports looks like:I'm not sure why the
uuid
statement gets areturn
at the front whilepako
doesn't, but I wonder if this asymmetry is having some effect.