- From: Joe Pea via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Jun 2021 17:00:12 +0000
- To: public-css-archive@w3.org
Honestly though, I'm not sure detached mode is a good idea. Just imagine objects escaping the browser plane will interfere with the host UI and cause bad UX. We can't predict what host UIs will be like. Oculus, for example, has UI outside of the browser right next to the browser window, on both sides. _It would be bad for web authors to interfere with usability of these host objects._ I believe users should opt into a 3D experience like the do with WebXR. Besides that, there are other significant issues: --- I sincerely ask for spec authors to please not work on this feature and instead focus on figuring out why the current specs lead to all browsers having broken CSS 3D implementations. Otherwise, this will be yet another _never use this feature, it will lead to bad user experiences_ type of thing. I'm literally not going to use this feature in a production-quality applications if the current problems exist. I could go dig up issues if you need, but for starters, try this: https://keithclark.co.uk/labs/css-fps/ It is glitchy as heck in Chrome, sadly. Firefox looks pretty good nowadays, but the performance is absolutely horrible. When you compare CSS 3D to other commercial 3D systems, they put browsers to shame. _We can't move forward with that_. I just can't imagine wanting to use `detached` with these existing problems, risking to have users think I write glitchy junk, when actually it is out if my control as an end web developer, inside the browser CSS engine. It would be best to focus on 1. what about the current spec leads to the current browser problems and fixing those, and 2. getting CSS 3D into WebXR space. This would be very valuable, giving use the ability to mix it with WebGL content (assuming the glitchy jank is solved). 3. getting WebXR into that `detached`-like mode. - This would mean one could export WebXR scenes outside of the browser plane, very much like the `tranform:detached` idea, but with the ability to draw 3D objects using the _**reliable**_ WebGL API. CSS 3D (after it is fixed) inside of WebXR is where the magic will be. As an example of WebGL content mixed with CSS 3D, see these: - https://codepen.io/trusktr/pen/rpegZR - https://codepen.io/trusktr/pen/RLLogx - https://codepen.io/trusktr/pen/RjzKJx - https://codepen.io/trusktr/pen/OzJJJN - https://codepen.io/spirodonfl/pen/vYgPzoK - https://codepen.io/trusktr/pen/rNMdamE - https://codepen.io/trusktr/pen/YzGRNzq - https://codepen.io/trusktr/pen/abmQgBg Being able to do this in WebXR, without glitches, and performantly, would be a lot more valuable than `detached`. -- GitHub Notification of comment by trusktr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4242#issuecomment-852288201 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 June 2021 17:00:46 UTC