Manual: added importmap support

[ycw]

Related issue: #23363

• added importmap in two files (here, there)

• transform assets' path from abs to rel; asset includes script,link,iframe,img in manual//.html and manual//.js

• iframe is sandboxed ( forbid export-to, and open-external, those buttons are noop, for now )

• use es-module-shim shim-mode, no errors will be prompted.

Preview:

• on github
• on githack

[mrdoob]

Ops! Could you resolve the conflicts?

[ycw]

@mrdoob I'm not sure how to 455 conflicts..

[greggman]

A few comments:

• There's no reason to sandbox these iframes. The only reason to sandbox iframes is because the page is a page you log into and/or contains user content. These pages are static HTML. The site is 100% in control of what goes in them

• It's hard to see what all the changes are here but they don't handle the OffscreenCanvas article (https://ycw.github.io/three.js/manual/#en/offscreencanvas)

• I'm confused at which direction this is going. It seems like it's reverting adding the import maps to the files in manual/examples.

• If I try to run any of those examples on their own, they don't run. (eg: https://ycw.github.io/three.js/manual/examples/cameras-perspective.html).

• If I click "open in a separate window" under any sample it fails to open

• If I right click on "open in a separate window" and pick "open in a new tab" the url is wrong

• As for the relative paths, I'd suggest if you want relative paths do that in a single PR, separate from all any other changes.

[ycw]

@mrdoob @greggman

There's no reason to sandbox these iframes. The only reason to sandbox iframes is because the page is a page you log into and/or contains user content. These pages are static HTML. The site is 100% in control of what goes in them

it seems a generated form is sent to external domains, true?

I'm confused at which direction this is going. It seems like it's reverting adding the import maps to the files in manual/examples.

import-maps is a draft, esms is influx, hard coding map and polyfill in many places is not a good idea for now.

If I try to run any of those examples on their own, they don't run.
.. If I click "open in a separate window" under any sample it fails to open
.. If I right click on "open in a separate window" and pick "open in a new tab" the url is wrong

I thought the examples are data files for the editor, the sources (html/css/js) have been clearly displayed in each pane. I'm not sure what the motivation of 'open in separate window'. ( wait..., is the popup window in sync with the editor in realtime? )

As for the relative paths, I'd suggest if you want relative paths do that in a single PR, separate from all any other changes.
It's hard to see what all the changes are here but they don't handle the OffscreenCanvas article

I agree, I might PR this.

[Mugen87]

Closing. Please split up your changes into smaller PRs.