[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] Behavior of WebGL canvas when it can't make a backbuffer of the requested size?



On Sep 28, 2010, at 6:17 PM, Steve Baker wrote:

> Isn't there a deeper problem here?  If the underlying hardware has a
> limit on the size of an OpenGL/Direct3D rendering context - and the new
> generation of browsers are using the GPU to do compositing, isn't it the
> case that the browser window (or at least the canvas) will also be
> limited in size?
> 
> If so, then wouldn't the idea of rendering at less-than-requested
> resolution then resizing in the compositor also be impossible?

Browsers solve this with tiling. A WebGL author could certainly do tiling (although it would be very hard). But we can't make that functionality required.

-----
~Chris
cmarrin@apple.com




-----------------------------------------------------------
You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email: