[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] Ambiguity and Non-deterministicness in the WebGL Spec
On 2010-12-16 02:31, Chris Marrin wrote:
On Dec 13, 2010, at 6:42 PM, Mark Callow wrote:
On 14/12/2010 03:57, Chris Marrin wrote:
A lazy clear operation implies a single clear to the current values set in the state. So isn't that violating the spec. that you just wrote: "clears the buffers to their default values"?
On 12/12/2010 04:20 PM, Gregg Tavares (wrk) wrote:
The spec has changed to effectively require a clear each time the
WebGL draw buffer is composited
WebGL presents its drawing buffer to the HTML page compositor
immediately before a compositing operation, but only if the
drawing buffer has been modified since the last compositing
operation. Before the drawing buffer is presented for compositing
the implementation shall ensure that all rendering operations have
been flushed to the drawing buffer. By default, after compositing
the contents of the drawing buffer shall be cleared to their
default values. This includes the color buffer as well as the
depth and stencil buffers if they are defined
Note that I don't say that the buffers are cleared to the current clear values in the state. This was intentional to make it clear that the state is not involved in this clear operation. But this clear operation can be done lazily. If the author first clears the buffers first (which will almost always be the case), then this clear can be skipped. Using the word "default" is really only a placeholder. We need to make it clear that it is the default value from the state, which I believe is well defined in the GLES spec.
I'm not sure what you mean by that, but I like where you're going below...
I think that we should use the proposal you wrote in another message in this thread:
We could always say that the drawing buffers have values that are "undefined but guaranteed NOT to contain information from another process", or something like that.
I added the emphasized "not" as I think you inadvertently omitted it.
Yep, my mistake.
So I'd rewrite as "By default (what does that mean? ed) after compositing the contents of the drawing buffer are undefined but are guaranteed not to contain information from another process." Then add a non-normative note somewhere that "One way to an implementation can guarantee buffers do not contain information from another process is to clear the buffer to the default values specified in OpenGL ES."
This gives maximum flexibility to the implementation while maintaining security.
These words sound good. I have incorporated them into the spec in section 2.2.
Like I said in a previous mail I think this is a mistake. Leaving it
undefined essentially means you will have to check what the most common
implementations are doing and do the same thing. If you do anything else
there is a high probability that content will not work since it relies
on the behavior of the most common implementations.
Saying something is undefined does not mean implementations can choose
to do whatever they want. If most desktop implementations keep the old
value, which would be compliant with the spec and not very surprising
since you need to be able to do that in the other mode, you can probably
not make the optimizations you want on mobile without breaking content,
even if you are still compliant with the spec.
You are currently subscribed to email@example.com.
To unsubscribe, send an email to firstname.lastname@example.org with
the following command in the body of your email: