- From: Blair MacIntyre <bmacintyre@mozilla.com>
- Date: Sun, 19 Aug 2018 12:29:09 -0700
- To: public-immersive-web@w3.org, Cecile Muller <contact@wildpeaks.fr>
- Message-ID: <CADvj9uxH+58vtdmi6_sMLU0Z7nqxj4y34-KC2e4UM+4warBhKg@mail.gmail.com>
Can I make a modest suggestion: can the discussions in this email thread be moved to GitHub issues? Email is a terrible medium for this (it’s ephemeral, people who aren’t on the lists can see or contribute, it’s really hard to follow some of the threads, etc). There is some really good stuff being said, some good suggestions, and I’d hate for it to be lost. -- Blair MacIntyre Principal Research Scientist bmacintyre@mozilla.com https://pronoun.is/he/him https://blairmacintyre.me On August 19, 2018 at 2:59:42 PM, Cecile Muller (contact@wildpeaks.fr) wrote: Good evening, Just adding a few cents as webdev and long time VRML author. When talking 3D content embedded in HTML, the obvious pick would go for the existing <link rel="icon"/> tag as it already evolved over the years to accept more than just .ico files, so why not allow it to reference 3d files as well. There are even people using canvas to generate animated favicons, although I'm not sure if that's still supported (I think it is). However, it could be interesting to also have a response header equivalent (similar to how googlebot directives can be specified either with a <meta> tag, either with a header), because it would allow specifying a favicon for contents that are not text/html (e.g. 3d websites). If the issue is progressive enhancement or not being able to choose between file formats, we could be inspired by <img srcset> that provides multiple versions of an image based on media queries (or how the <video> tag can provide multiple <source> so the browers can pick a source that uses a codec the browser can read). If 3D display was a media query rule usable with "@supports", it would allow web authors to display optimized content the same say they can optimize for small screen vs large screen. As for VRML favicons, I can't talk for the others but BSContact never had a rule of using a home.wrl file afaik, we just used the regular HTML site favicon because it was based on iexplore internally back when it was a browser plugin. See you, Cecile
Received on Sunday, 19 August 2018 19:29:33 UTC