Apple proposes adding "model" element to HTML that displays 3D content
1–10 of 241 posts
Re: Apple proposes adding "model" element to HTML that displays 3D content
#2Rendered data is not exposed to / extractable by the page in this proposal, so no tainting is required. We do expect this would require extensions to Fetch (a new destination type), Content Security Policy (a new policy directive), and likely a few others.
I do buy 3d model data occasionally (hobby, not for professional uses). I think most stores obfustcate the data somehow although I never took a look at it in detail. If you wanted, you probably could easily extract the model from the preview.
I still think this is a very bad proposal. Why compare something with an image and then disallow it to be treated like other ressources? This is typically bad corporate influence on the web.
I think we should go the other way. Remove DRM components from browsers again. Netflix not available anymore? They will either adapt or not be available. Their loss would probably be more significant.
Re: Apple proposes adding "model" element to HTML that displays 3D content
#3Re: Apple proposes adding "model" element to HTML that displays 3D content
#4> Privacy considerations Rendered data is not exposed to / extractable by the page in this proposal, so no tainting is required. We do expect this would require extensions to Fetch (a new destination type), Content Security Policy (a new policy directive), and likely a few others. I do buy 3d model data occasionally (hobby, not for professional uses). I think most stores obfustcate the data somehow although I never t…
Because webgl fingerprinting. Also, I'm not sure why you think not being able to extract the data using javascript is "bad corporate influence on the web" or" DRM". you can still do whatever you want. The models are freely available for you just not the page.
Re: Apple proposes adding "model" element to HTML that displays 3D content
#5Re: Apple proposes adding "model" element to HTML that displays 3D content
#6Interesting they show support for USD(Z) in the example. USD will be the standard for most VFX houses and make tooling for various web based systems so much easier.
Re: Apple proposes adding "model" element to HTML that displays 3D content
#7Re: Apple proposes adding "model" element to HTML that displays 3D content
#8Re: Apple proposes adding "model" element to HTML that displays 3D content
#9Interesting they show support for USD(Z) in the example. USD will be the standard for most VFX houses and make tooling for various web based systems so much easier.
https://graphics.pixar.com/usd/docs/
The closest thing I can find there is the glossary and the C++ doxygen api docs.
Re: Apple proposes adding "model" element to HTML that displays 3D content
#10> Privacy considerations Rendered data is not exposed to / extractable by the page in this proposal, so no tainting is required. We do expect this would require extensions to Fetch (a new destination type), Content Security Policy (a new policy directive), and likely a few others. I do buy 3d model data occasionally (hobby, not for professional uses). I think most stores obfustcate the data somehow although I never t…