Re: AR Web

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