Hi, Henrik

Seems I found the cause.

I have the snippet below in my (pre-ES6) code.

$interval is an Angular.js service and what the snippet pattern does is just

running only once after it's first execution (granting the iframe is loaded)

var stop = $interval(function() {
    postMessage(...);
    ... snip ...
    postMessage(...);
    $interval.cancel(stop);
}, 1500);

I used before a time of only 250 ms. It's not enough anymore - need to investigate why,
as just increasing a delay is not satisfactory.

After increasing it to 1.5 s, all commands completed successfully.

Thanks very much for your support and valuable suggestions!

Hello Henrik,

I'm still having problems. I ran out of ideas for now.

Seems ESA Sky is ignoring my calls:

I tested with the calls you passed. Seems none were executed.

I just saw the random image ESASky always show when started.

I then thought about the possibility of any error when doing more than one call (i.e. an error occurred as result of one of them and subsequent ones failed too as consequence) and tried with just one simple call, say goToRaDec (with valid RA and Dec, of course). No results too.

I did my tests locally. I switched to http again (https seems to have nothing to do with the problem anyway)

I'm using Chrome Version 133.0.6943.53 (Official Build) (64-bit)

My OS is a 64-bit Ubuntu 22.04.5 LTS

It functioned fine in the past, with multiple commands and all that.

To reduce the possibility of missing a bug on my side, I tested with the code as it were (for I did many changes trying to figure the problem out).

I also tried keeping the code at minimum to see if I could isolate any bug I was not seeing.

Here's the possible relevant errors and warnings I picked with Chrome:

esasky_cl_7_1_2025_0…07_38Z.nocache.js:4

[Violation] Avoid using document.write(). https://developers.google.com/web/updates/2016/08/removing-document-write

esasky/:1

[GroupMarkerNotSet(crbug.com/242999)!:A0E03801BC360000]Automatic fallback to software WebGL has been deprecated. Please use the --enable-unsafe-swiftshader flag to opt in to lower security guarantees for trusted content.

sky.esa.int/esasky/?target=190.91669999999993%2011.552611111111112&hips=DSS2+color&fov=0.3&projection=SIN&cooframe=J2000&sci=true&lang=en:1

[GroupMarkerNotSet(crbug.com/242999)!:A0E03801BC360000]Automatic fallback to software WebGL has been deprecated. Please use the --enable-unsafe-swiftshader flag to opt in to lower security guarantees for trusted content

aladin.min.js:20

GET https://cdn.skies.esac.esa.int/DSSColor//Moc.fits" class="redactor-autoparser-object">https://cdn.skies.esac.esa.int/DSSColor//Moc.fits net::ERR_FAILED 404 (Not Found)

esasky_cl_7_1_2025_02_07T10_07_38Z-0.js:7148

GET https://sky.esa.int/esasky-tap/ext-taps?ACTION=REQUEST&ADQL=SELECT%20*%20FROM%20ivoa.ObsCore&MAX_REC=1&TAP_URL=https://ws.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/argus/sync 500 (Internal Server Error)

esasky_cl_7_1_2025_0…10_07_38Z-0.js:7148

GET https://sky.esa.int/esasky-tap/ext-taps?ACTION=REQUEST&ADQL=SELECT%20*%20FR…e&MAX_REC=1&TAP_URL=https://ws.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/argus/sync 500 (Internal Server Error)

Regarding the 404 error: the link Associated coverage map: MOC is broken in https://cdn.skies.esac.esa.int/DSSColor/

Could you confirm if there's anything on your side?

Cheers,

Bruno

Thanks, Henrik, for the fast answer!

Just one more doubt:
I'm doing successive calls to 'setCooFrame', 'goToRaDec', 'setFov', and finally 'changeHipsWithParams'
These calls were working fine previously, but now it seems just the first one of them is being executed...

I tried adding a small interval between the calls, using promises, making sure the frame was fully loaded before firing these commands and nothing worked.

Was there any change in ESASky that could be the cause of this and I need to adapt my code accordingly?

I thought if this was so because I did my tests without loading (but It functioned offline before) or because I did not use HTTPS in my server (but I'm using it now).

Another thing: the properties file of a HiPS includes info like frame, initial ra, dec and fov. When I load a HiPS file in ESASky do I need to always set those via calls to ESASky or is there any way for ESASky to pick them from the HiPS parameters? I suspect the best would be to read them in the properties myself and fire the related events.

Sorry for these newbie questionings.

Best regards,
Bruno