Hi Justin,
I will do reach out to some developers to see if they think it's useful.
As an experiment, I wrote a javascript polyfill that implements a rough
version of my proposal.
I took a box 2d example and ported it over. Since it draws to canvas under
the hood, I didn't have to change any code
On 19 Oct 2013 at 18:27, Ms2ger wrote:
> Quoting part of the original email you trimmed:
>
>> Luckily, we have SVGSVGElement.prototype.getElementById available to
>> compare to Element.prototype.querySelector.
>
> That is, getElementById is available on |svg| elements in the SVG namespace.
Yeah
Hi Tim,
On 10/19/2013 07:03 PM, Tim Streater wrote:
On 18 Oct 2013 at 22:56, Boris Zbarsky posted, inter alia,
this code:
[1] The testcase:
document.write("
On 10/18/13 5:56 PM, Boris Zbarsky wrote:
I used a fairly large subtree that needs walking (1000
elements)
Er, I _meant_ to, but the testcase clearly only has 100 elements.
The numbers with 1000 elements are:
Chrome:
document.getElementById: 50
In-tree querySelector: 210
In-tree querySelector
On Sat, Oct 19, 2013 at 1:28 AM, Glenn Maynard wrote:
> I'd like to hear thoughts on the "context.attachToCanvas" approach. I
> think it has important advantages over ImageBitmap:
>
> - ImageBitmap requires the user to call close(). If the user forgets, or
> doesn't know, or misses it in some c
