On Tue, Feb 16, 2010 at 07:25:34PM +, Stefan Haustein wrote:
We've been getting pretty good traction on Vlad's ArrayBuffers proposal,
which was taken from the WebGL spec. Our current plan is to change the
names in the browsers (WebKit, Chrome and Mozilla) to the non-WebGL
On Wed, Feb 17, 2010 at 8:35 AM, Stef Epardaud s...@epardaud.fr wrote:
On Tue, Feb 16, 2010 at 07:25:34PM +, Stefan Haustein wrote:
We've been getting pretty good traction on Vlad's ArrayBuffers
proposal,
which was taken from the WebGL spec. Our current plan is to change
the
On Wed, Feb 17, 2010 at 1:04 PM, Stefan Haustein haust...@google.comwrote:
On Wed, Feb 17, 2010 at 8:35 AM, Stef Epardaud s...@epardaud.fr wrote:
On Tue, Feb 16, 2010 at 07:25:34PM +, Stefan Haustein wrote:
We've been getting pretty good traction on Vlad's ArrayBuffers
proposal,
The FormData object [1] is a great way to allow multipart/form-data
encoded content to be submitted using XMLHttpRequest. It would be
great if it was possible to get a FormData object representing the
data contained in a form. This in order to allow normal HTML forms
being used, but using
On Thu, 18 Feb 2010 00:15:25 +0100, Jonas Sicking jo...@sicking.cc wrote:
So I suggest we add a method like
interface HTMLFormElement : HTMLElement {
...
FormData getFormData();
...
};
Should we name it toFormData() instead for consistency with canvas? Or
is canvas inconsistent with
