Map popup blocked in place explorer starter popup window

[tivup]

Description of the bug:

the google maps link is blocked when clicking on expanded view or any link that pops up in a new window when using the maps explorer starter app. I’m using latest dev chrome on a mac, Version 135.0.7023.0 (Official Build) dev (x86_64)

The response header had the following:
The document was blocked from loading in a popup opened by a sandboxed iframe because this document specified a cross-origin opener policy.

I had the latest stable chrome and saw this same behavior there. I’m now seeing it in the latest dev release as well

is this a known issue or do i need to figure out what’s going on in my case.

Thanks!

Actual vs expected behavior:

No response

Any other information you'd like to share?

No response

[mindtd]

Understand from document "versions included here can run standalone", and there is no package.json or npm requirement, how do we run the Map Explorer as standalone locally?

Attempted: 1) open with Chrome or Edge browsers / 2) run in terminal: start index.html,

• get a blank webpage
• Developer Tools 2 errors: 1) Access to script at 'file:///C:/Users/Name/starter-applets/maps/script.js' from origin 'null' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: chrome-extension, chrome-untrusted, data, edge, http, https, isolated-app. 2) Failed to load resource: net::ERR_FAILED

Update on progress made

Resolution partially - start local server (courtesy of Gemini): python -m http.server and http://localhost:8000 did the map.

Q: how do I get the System Instructions and Prompt (on the Left) of Starter Apps up?

Missing LHS - npm install followed by npm run dev for spatial-applet encounters the same issue.

Missing LHS - npm install followed by npm run dev for video-applet runs into the same issue and warning messages.

video-applet@0.0.0 dev
node --env-file=.env server/index.mjs

1:46:35 PM [vite-express] Running in development mode
1:46:36 PM [vite-express] Using Vite to resolve the config file
Server is listening...
Deprecation Warning [legacy-js-api]: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.

More info: https://sass-lang.com/d/legacy-js-api

Deprecation Warning [import]: Sass @import rules are deprecated and will be removed in Dart Sass 3.0.0.

More info and automated migrator: https://sass-lang.com/d/import

╷
1 │ @import './player.sass'
│ ^^^^^^^^^^^^^^^
╵
src\styles\main.sass 1:9 root stylesheet

Deprecation Warning [import]: Sass @import rules are deprecated and will be removed in Dart Sass 3.0.0.

More info and automated migrator: https://sass-lang.com/d/import

╷
2 │ @import './chart.sass'
│ ^^^^^^^^^^^^^^
╵
src\styles\main.sass 2:9 root stylesheet

[tivup]

@mindtd did you mean to post this here? I don't think this is relevant to my original question.

The issue is obviously with the starter app and i don't think the starter team cares lol. I think they're just meant to be starters and you build on them regardless of whether the starter works or not :)

I don't think I can close this out but please feel free to ignore and archive - there are better tools out there.

[mindtd]

@tivup I misinterpreted and appreciate the clarification.