Re: [w3ctag/design-reviews] CORS Requirement for 3rd party sources in <model> tag (Issue #775)

> And then accepting the ongoing maintenance cost of that

As @plinss mentioned, we have to do that anyway for legacy technologies like "image, video, audio, and script elements" .

> There might also be problems with service workers. To get the same kind of isolation as `iframe` has the server serving the model would also have to run the service worker, which strikes me as not the kind of thing a web developer would expect.

It's the same isolation as `<img>` or `<video>`. Why would it be like `<iframe>`?

>  They would expect 3D models to be similar to images or style sheets.

Indeed. If the author wants access to the contents of the model, cors is needed. If it's rendered by the browser/compositor and no pixel access is allowed, cors is not needed. As you say, authors would expect 3D models to be similar to images.





-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/775#issuecomment-1279128725
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/775/1279128725@github.com>