+1 to this: I would be very interested in any plausibly realistic testcase causing Firefox to spend significant time in drawElements validation.
Until it's proven that drawElements is necessarily slow in some cases regardless of implementation in particular browsers, we're just talking about the possibility of browser bugs here. We don't want to add Web APIs to query "is the browser buggy" --- Might as well add a isComputerOn() function.
Firefox's drawElements validation code is here:
There's nothing really fancy here, it's just a binary heap, i.e. a binary tree of integers stored in a compact way in an array.
On 14-03-11 11:27 AM, Brandon Jones wrote: