On 11/29/09 12:15 AM, Kenneth Russell wrote:
I assume you meant JS bitwise operators? Do we have any indication that
this would be faster than four array property sets? The bitwise ops in JS
are not necessarily particulary fast.
Yes, that's what I meant. I don't have any data on whether this
Philip,
It's great to see further specifications come up around captions. I do
think we need these to make progress and come to a specification that
we can all agree on.
I just wanted to add a comment on your wiki page for clarification:
My wasn't supposed to stay a JavaScript implementation. I
On Sat, Nov 28, 2009 at 9:00 PM, Boris Zbarsky wrote:
> On 11/28/09 11:42 PM, Kenneth Russell wrote:
>>
>> From a technical standpoint, it would be feasible to use the
>> "WebGLUnsignedIntArray" to access the Canvas's pixel data, and
>> assemble RGBA pixels into integer values using just JavaScrip
On 11/28/09 3:44 PM, Jason Oster wrote:
The trouble with profiling my project is that it is a XULRunner
application, and does not run directly in web browsers as-is.
This is not an issue at all; any XULRunner application can be run in
Firefox directly (with the right command-line flags). I'm
On 11/28/09 11:42 PM, Kenneth Russell wrote:
From a technical standpoint, it would be feasible to use the
"WebGLUnsignedIntArray" to access the Canvas's pixel data, and
assemble RGBA pixels into integer values using just JavaScript logical
operators.
I assume you meant JS bitwise operators? Do
On Sat, Nov 28, 2009 at 12:44 PM, Jason Oster wrote:
>
> Once again, I agree. My confusion on the type-specific arrays for WebGL is
> that they were specific and general enough to use in other cases. If they
> should not be used in 2D canvas implementations (or elsewhere) then a
> 2D-canvas-spec
My apologies for the direct reply, Oliver. This was meant to go back to the
list:
On Nov 26, 2009, at 3:35 PM, Oliver Hunt wrote:
> WebGL has completely different constraints to that of the 2d canvas -- when
> the developer provides resources to GL the developer has to provide a myriad
> of t
As part of the work in the W3C HTML Accessibility Task Force I have
proposed a new element to handle several use cases which are
currently not solved by HTML5 .
http://wiki.whatwg.org/wiki/Video_Overlay
Certainly we shouldn't be adding this to HTML5 at this point, but I think
HTML6 and be
We seem to be straying behind the bikeshed a little bit here. My point
wasn't to point out problems with the examples given in "common idioms
without dedicated elements"
http://www.whatwg.org/specs/web-apps/current-work/multipage/commands.html#conversations
The real problem is the definition
