On Tue, Dec 1, 2009 at 7:08 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
The @caption proposal isn't for an attribute on p only, but rather
for an attribute on any element that is a child of a figure. (It's
just that most of the time using a p is most appropriate.)
Ah, OK. Well, given the
On Dec 2, 2009, at 12:58 AM, Hugh Guiney wrote:
On Tue, Dec 1, 2009 at 9:58 PM, Maciej Stachowiak m...@apple.com
wrote:
It's not just rendering issues - all current browsers produce a
broken DOM
when you include legend outside of fieldset, ranging from
dropping the
legend element
On Wed, 02 Dec 2009 03:58:32 +0100, Maciej Stachowiak m...@apple.com
wrote:
On Dec 1, 2009, at 4:08 PM, Tab Atkins Jr. wrote:
On Tue, Dec 1, 2009 at 6:01 PM, Hugh Guiney hugh.gui...@gmail.com
wrote:
Is there a reason we can't reuse legend (or label)? I don't think
giving p an attribute
Summary: I haven't removed the storage mutex, but I did adjust when it is
released slightly to handle some cases that had been missed before.
On Thu, 29 Oct 2009, Darin Fisher wrote:
On Mon, Oct 12, 2009 at 7:07 PM, Ian Hickson i...@hixie.ch wrote:
the problem here is that localStorage
6.11.9, step 3.1:
To me, this text:
If the browsing context is a top-level browsing context
(and not an auxiliary browsing context)
seems to imply that an auxiliary b-c is not a top-level b-c.
This is subjective of course, but it might be a good thing to
rephrase the sentence
On Wed, Dec 2, 2009 at 2:06 AM, Ian Hickson i...@hixie.ch wrote:
On Tue, 3 Nov 2009, Jeremy Orlow wrote:
If we do this, we need to re-visit ways that scripts can tell whether
the lock has been dropped. I can't remember which idea was most in
favor last time we talked about it, but a
On Wed, 2 Dec 2009, Jeremy Orlow wrote:
On Wed, Dec 2, 2009 at 2:06 AM, Ian Hickson i...@hixie.ch wrote:
On Tue, 3 Nov 2009, Jeremy Orlow wrote:
If we do this, we need to re-visit ways that scripts can tell
whether the lock has been dropped. I can't remember which idea was
most
We've been watching our colleagues build native apps that use speech
recognition and speech synthesis, and would like to have JavaScript
APIs that let us do the same in web apps. We are thinking about
creating a lightweight and implementation-independent API that lets
web apps use speech services.
On Wed, Dec 2, 2009 at 3:32 AM, Bjorn Bringert bring...@google.com wrote:
We've been watching our colleagues build native apps that use speech
recognition and speech synthesis, and would like to have JavaScript
APIs that let us do the same in web apps. We are thinking about
creating a
Is speech support a feature of the web page, or the web browser?
On Wed, Dec 2, 2009 at 12:32 PM, Bjorn Bringert bring...@google.com wrote:
We've been watching our colleagues build native apps that use speech
recognition and speech synthesis, and would like to have JavaScript
APIs that let us
I think that it would be best to extend the browser with a JavaScript
speech API intended for use by web apps. That is, only web apps that
use the speech API would have speech support. But it should be
possible to use such an API to write browser extensions (using
Greasemonkey, Chrome extensions
Hi WHATWG members,
This was posted by Akatsuki Kitamura on the W3C Japanese Interest
Group Mailing List.
The section 9.2.1 of HTML5 spec says;
Start tags must have the following format:
1. The first character of a start tag must be a U+003C LESS-THAN SIGN
character ().
2. The next few
On Wed, Dec 2, 2009 at 9:17 AM, Bjorn Bringert bring...@google.com wrote:
I think that it would be best to extend the browser with a JavaScript
speech API intended for use by web apps. That is, only web apps that
use the speech API would have speech support. But it should be
possible to use
I missunderstood too. It would be great to have the ability to access
the microphone and record+upload or stream sound to the web server.
--
D.
On Wed, 2009-12-02 at 10:04 -0800, Jonas Sicking wrote:
On Wed, Dec 2, 2009 at 9:17 AM, Bjorn Bringert bring...@google.com wrote:
I think that it
I agree that being able to capture and upload audio to a server would
be useful for a lot of applications, and it could be used to do speech
recognition. However, for a web app developer who just wants to
develop an application that uses speech input and/or output, it
doesn't seem very convenient,
On Wed, 02 Dec 2009 12:32:07 +0100, Bjorn Bringert bring...@google.com
wrote:
We've been watching our colleagues build native apps that use speech
recognition and speech synthesis, and would like to have JavaScript
APIs that let us do the same in web apps. We are thinking about
creating a
If you're able to read from the mic, you don't need to upload. You could
save it locally (for example for voice memos). The read+upload was just
2 steps I sugested instead of direct streaming. Speech recognition could
be done separatly. One could use the mic to capture a voice note. Other
could
Currently, the Web Sockets API spec says that the WebSocket.URL
attribute must just return a value that was passed to the WebSocket
constructor. This doesn't match how many other url accessors work, and
consequentially, it doesn't match what currently happens in WebKit.
I think it makes
On Wed, Dec 2, 2009 at 11:17 AM, Bjorn Bringert bring...@google.com wrote:
I agree that being able to capture and upload audio to a server would
be useful for a lot of applications, and it could be used to do speech
recognition. However, for a web app developer who just wants to
develop an
We're envisaging a simpler programmatic API that looks familiar to the
modern Web developer but one which avoids the legacy of dialog system
languages.
Dave
On Wed, Dec 2, 2009 at 7:25 PM, João Eiras jo...@opera.com wrote:
On Wed, 02 Dec 2009 12:32:07 +0100, Bjorn Bringert bring...@google.com
On Thu, 03 Dec 2009 01:50:20 +0100, Dave Burke davebu...@google.com
wrote:
We're envisaging a simpler programmatic API that looks familiar to the
modern Web developer but one which avoids the legacy of dialog system
languages.
Ok. I referenced that XHTML+Voice because there is already a
On 28/10/2009, at 1:10 PM, Aryeh Gregor wrote:
On Tue, Oct 27, 2009 at 7:40 PM, Kit Grose k...@iqmultimedia.com.au wrote:
Can I get some sort of an understanding on why this behaviour (non-
descript error in supported UAs rather than using the fallback content
that can provide alternate
Hi all
Could you please see the section in the spec?
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html#the-input-element
There is a table which includes summarizes which of content attributes, IDL
attributes, methods, and events apply to each state.
Is the value
I've question about thread to run Web Socket feedback from the protocol.
If server sends back handshake response and a data frame, and close
immediately, fast enough to run JavaScript on browser, how readyState should
be?
1) When client recognizes handshake response header, it changes readyState
24 matches
Mail list logo
