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

Re: [Public WebGL] about the VENDOR, RENDERER, and VERSION strings



On Wed, Dec 1, 2010 at 7:25 PM, Benoit Jacob <bjacob@mozilla.com> wrote:
> ----- Original Message -----
>> These are the ones that are likely to vary on the desktop
>>
>> MAX_COMBINED_TEXTURE_IMAGE_UNITS
>> MAX_CUBE_MAP_TEXTURE_SIZE
>> MAX_FRAGMENT_UNIFORM_VECTORS
>> MAX_RENDERBUFFER_SIZE,
>> MAX_TEXTURE_IMAGE_UNITS
>> MAX_TEXTURE_SIZE
>> MAX_VARYING_VECTORS
>> MAX_VERTEX_ATTRIBS,
>> MAX_VERTEX_TEXTURE_IMAGE_UNITS
>> MAX_VERTEX_UNIFORM_VECTORS
>> MAX_VIEWPORT_DIMS,
>>
>>
>> I suspect there are an average of 3 bits of information for each of
>> those (meaning 5-8 variations) which would be`11*3 or 33 bits of info.
>>
>>
>> It's possible that many combinations don't exist though
>
> The combination of these parameters is a function of the graphics card, and there are only 2^9 graphics cards, so really there are at most 9 bits of info there (99.999999% these 2^33 combinations don't exist).

The caps could be affected by driver and OS as well.  Also Steve makes
a good point about extensions.

Coming back to the RENDERER string question for Firefox -- for the
purposes of invading privacy, bits obtained via gl.get and gl
extensions are just as good as bits obtained from getString(RENDERER),
and in practice will be highly redundant with the bits from RENDERER.
On the other hand, the bits from RENDERER have extra value to WebGL
authors and users, because they will help characterize performance,
and allow workarounds for bugs in certain implementations.

Unless FF plans on crippling gl.get and gl extensions, hiding the
RENDERER info is just punishing the WebGL community, for no privacy
benefit.

-T
-----------------------------------------------------------
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: