Nicola Di Fabrizio wrote:
is it possible to set a attribute for checking the element
if it is not empty
Yes, there's the attribute required, see
http://www.whatwg.org/specs/web-apps/current-work/multipage/common-input-element-attributes.html#the-required-attribute
like
input type=text
Since Ian seems to prefer to jumble all threads on a given group of
issues together in one message, I'll attempt to use the same format this
time.
On 04/12/11 04:09, Ian Hickson wrote:
On Tue, 29 Mar 2011, Harald Alvestrand wrote:
A lot of firewalls (including Google's, I believe) drop the
On 04/08/11 18:51, Glenn Maynard wrote:
On Fri, Apr 8, 2011 at 4:41 AM, Harald Alvestrand
har...@alvestrand.no mailto:har...@alvestrand.no wrote:
My alternate proposal:
--
The initialization string looks like this:
{
See:
http://www.whatwg.org/specs/web-apps/current-work/multipage/common-input-element-attributes.html#the-required-attribute
-Original Message-
From: Nicola Di Fabrizio
Sent: Wednesday, April 13, 2011 9:41 AM
To: whatwg@lists.whatwg.org
Subject: [whatwg] question about the input tag
thanks a lot for the fast response, it is exactly what i search
nicola di fabrizio
-Original Message-
From: Ian Hickson [mailto:i...@hixie.ch]
Sent: den 12 april 2011 04:09
To: whatwg
Subject: [whatwg] PeerConnection feedback
On Tue, 29 Mar 2011, Stefan H kansson LK wrote:
The web application must be able to define the media format to
be used for the
On 04/13/11 13:35, Stefan Håkansson LK wrote:
-Original Message-
From: Ian Hickson [mailto:i...@hixie.ch]
Sent: den 12 april 2011 04:09
To: whatwg
Subject: [whatwg] PeerConnection feedback
On Tue, 29 Mar 2011, Stefan H kansson LK wrote:
The web application must be able to define the
On Fri, Apr 8, 2011 at 10:26 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 4/8/11 1:54 PM, Tab Atkins Jr. wrote:
In the legacy color parsing algorithm [...]
Could we change those two steps to just say If keyword is a valid CSS
color value, then return the simple color corresponding to that
() call,
throw an exception from getContext() in this case, or do something
else. Do you have a suggestion on which way to proceed?
-Ken
[1] http://krijnhoetmer.nl/irc-logs/whatwg/20110413#l-77
[2]
http://dev.w3.org/html5/spec/the-canvas-element.html#dom-canvas-getcontext
--
Glenn Maynard
On Wed, Apr 13, 2011 at 05:16, Kenneth Russell k...@google.com wrote:
(...)
To sum up, in general I think that whenever getContext(webgl)
returns null, it's unrecoverable in a high quality WebGL
implementation.
Makes sense.
Applications could detect all possible context creation failure
Hello All,
Gecko 2.0 ships with a non-standard method on canvas named
mozGetAsFile(contentType, fileName). We added this for internal use in our
UI. It retrieves the contents of the canvas as a File object (at the time
Gecko did not supports Blobs) encoded in the contentType according to the
On Wed, Apr 13, 2011 at 6:02 PM, Kyle Huey m...@kylehuey.com wrote:
Gecko 2.0 ships with a non-standard method on canvas named
mozGetAsFile(contentType, fileName). We added this for internal use in our
UI. It retrieves the contents of the canvas as a File object (at the time
Gecko did not
I would be in favor of this.
In my recent app — http://mustachified.com — I used `mozGetAsFile` to
retrieve file from canvas, append it to form data and send to an external
service via cross-domain request.
When mozGetAsFile was not available, I had to build blob manually from
canvas' data url.
Shouldn't this api be async?
Returning a blob means that the size is available which implies a sync
operation.
dave
On Wed, Apr 13, 2011 at 3:02 PM, Kyle Huey m...@kylehuey.com wrote:
Hello All,
Gecko 2.0 ships with a non-standard method on canvas named
mozGetAsFile(contentType, fileName).
user frustration and provide them a path toward getting the
content to work.
Hixie says this is a bad idea, for security reasons, and that the UA should
just tell the user directly:
http://krijnhoetmer.nl/irc-logs/whatwg/20110413#l-1056
That said, the discussion lead to another approach:
Calling
/20110413#l-1056
That said, the discussion lead to another approach:
Calling canvas.getContext(webgl, {async: true}) will cause it to *always*
return an object immediately, without attempting to initialize the
underlying drawing context. This context starts out in the lost state.
As long as WebGL
On Thu, Apr 14, 2011 at 09:01, Kenneth Russell k...@google.com wrote:
Adding support for asynchronous initialization of WebGL is a good
idea, and should be proposed on public_webgl, but this discussion
should focus solely on improving the specification of the existing
synchronous
On Wed, Apr 13, 2011 at 9:01 PM, Kenneth Russell k...@google.com
wrote:Return a new object for contextId
Adding support for asynchronous initialization of WebGL is a good
idea, and should be proposed on public_webgl, but this discussion
should focus solely on improving the specification of the
18 matches
Mail list logo
