Re: 3d favicons

>
>
> But if you mean that a client-side application like in the link can't
> render a 3d icon,
> there is no reason the same "use canvas to render arbitrary contents for
> the favicon"
> can't be used with a canvas rendering a 3d object as well:
>  - First, read the url to the 3d model from the link tag
>  - Then, load the model in three.js (for example)
>  - Then on render, convert the canvas to base64 and put the image in the
> favicon
>
> It could even render shaders & postprocessing fine because it just
> screenshots the canvas to a base64 png.
>

This relies on a readback which will induce a pipeline stall, because in
order to perform the readback the GPU has to block the call in client space
until all pending operations have completed, thereby blocking all script
execution in JS until the GPU is no longer busy, it's very bad for
performance, especially if the icon isn't the only thing you're rendering.