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

Re: [Public WebGL] Propose moving EXT_disjoint_timer_query extension to community approved

That's a fair point. For one thing, I'd neglected to widely announce the availability of the draft extension in Chromium. Some of the interested parties noticed the bug report get updated ( http://crbug.com/345227 ), but I'm not sure how many people have tried it. If interested people would please give it a try in Chrome's Dev Channel, your feedback on it would be appreciated. It should finally be possible to get fine-grained timing of GPU-side work in WebGL.

On the more general topic, I think broader advertising of these draft extensions in browsers is what's needed. Until these extensions have been vetted, it seems to me that they shouldn't be exposed unconditionally, so almost inevitably, the feedback will have to come from interested developers who enable the extensions themselves and try them out.

(Unless you're talking about adding another step to the process like "provisional", where it can be exposed unconditionally, with the caveat that it might be removed or changed in the future. I can see arguments both for and against adding a step like that.)


On Fri, Oct 2, 2015 at 10:43 PM, Florian Bösch <pyalot@gmail.com> wrote:
I don't have a principal objection against moving to community approved. I do however have some concern that taking something out of draft where the public wasn't testing it, to community approved where it can't be changed or pulled back to draft has the potential to reveal bugs or specification deficiencies that're then harder to address. It's more a concern about the extension process after prefix avoidance, where we now lack a way to publicly expose draft extensions.

On Sat, Oct 3, 2015 at 7:32 AM, Kenneth Russell <kbr@google.com> wrote:
WebGL community,

I would like to propose moving WebGL's wrapper for the EXT_disjoint_timer_query extension to community approved:

Thanks to David Yen from the Chromium team, this extension is now implemented in Chromium behind the --enable-webgl-draft-extensions command line flag. With a final update to the conformance test [1] and a final change to the browser [2], there is now a fully spec compliant implementation of this extension.

Comments in favor or against?