- From: Dean Jackson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Sep 2019 21:46:38 +0000
- To: public-css-archive@w3.org
I guess I need the explainer because I'm not sure how this is supposed to work, or whether it is useful, or why anyone would want to do it. I assume the idea is that you're looking at a Web page in some AR/VR space, and you want the elements in that page to project out (or back) from the flat surface into the hosting space? Do you expect the hosting space to apply effects to the projected elements? For example, will they respond to lighting, cast shadows, etc? If so, that means the hosting space needs pixel access, which we can't allow. If not, the effect will look so weird it isn't worth doing. And what happens as 3d elements are scrolled into view (they were clipped by the viewport)? Do they all of a sudden appear in 3d space? Does half of them appear if they are partially clipped? And why is this just applying to CSS transforms? Wouldn't a better case be having WebGL objects from the page exist in the hosting space? My gut feeling is that we should continue to assume that CSS always projects onto a flat 2d surface. Within that surface you can emulate 3d sub-spaces, but the end result is always 2d. Just like the <canvas> element. -- GitHub Notification of comment by grorg Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4242#issuecomment-528101903 using your GitHub account
Received on Wednesday, 4 September 2019 21:46:39 UTC