- From: MetaHubbe via GitHub <noreply@w3.org>
- Date: Wed, 19 Nov 2025 19:26:54 +0000
- To: public-css-archive@w3.org
Right now, there is little or no difference. Browsers on VR- and 3Dtv-devices generally display web pages as flat surfaces. I think that will change in the future, but probably one step at a time. The steps I can see are: * stereoscopic video support * stereoscopic image support * spherical image / video support (but this is likely not displayed inside the browser window, and that might not need standardization in the same way.) * stereoscopic canvas / webgl support (quering this can be done with getContext, so probably doesn't need support here.) * stereoscopic css support (this means each element would have it's own depth) In an ideal world, each of these steps could be implemented separately, and their support would be signalled to the web page separately so that the web page can choose weather to use stereoscopic assets or not. There are existing standards for stereoscopic images and videos, canvas and css will need new standards for stereoscopic support AFAIK. Right now, we are mostly interested in stereoscopic video, but it makes sense to look forward and make sure that whatever come with doesn't immediately fall apart when new capabilities are added. Maybe the css query should be more like (sterescopic-capable: feature) where feature is one of image, video, canvas or css ? -- GitHub Notification of comment by MetaHubbe Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13119#issuecomment-3554298404 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 November 2025 19:26:54 UTC