Requirements for new work [Was: Re: Speech Recognition and Text-to-Speech Javascript API]

2012-01-09 Thread Arthur Barstow
On 1/9/12 11:12 AM, ext Olli Pettay wrote: On 01/09/2012 04:59 PM, Arthur Barstow wrote: As I indicated in [1], WebApps already has a relatively large number of specs in progress and the group has agreed to add some new specs. As such, to review any new charter addition proposals, I think we nee

Re: Speech Recognition and Text-to-Speech Javascript API - seeking feedback for eventual standardization

2012-01-09 Thread Olli Pettay
On 01/09/2012 06:17 PM, Young, Milan wrote: To clarify, are you interested in developing the entirety of the JS API we developed in the HTML Speech XG, or just the subset proposed by Google? Not sure if you sent the reply to me only on purpose. CCing the WG and XG lists. Since from practical p

Re: Speech Recognition and Text-to-Speech Javascript API - seeking feedback for eventual standardization

2012-01-09 Thread Olli Pettay
On 01/09/2012 04:59 PM, Arthur Barstow wrote: Hi All, As I indicated in [1], WebApps already has a relatively large number of specs in progress and the group has agreed to add some new specs. As such, to review any new charter addition proposals, I think we need at least the following: 1. Relat

Re: [CORS] Does "Origin" have to be included in the "Access-Control-Request-Headers" field?

2012-01-09 Thread Vladimir Dzhuvinov
On Sat, 2011-12-17 at 16:10 +0100, Anne van Kesteren wrote: > On Fri, 29 Jul 2011 14:25:07 +0200, Vladimir Dzhuvinov > wrote: > > Regarding "6. Resource processing model": [item 3] "A list of headers > > consisting of zero or more header field names that are supported by > > the resource.": > >

Re: Speech Recognition and Text-to-Speech Javascript API - seeking feedback for eventual standardization

2012-01-09 Thread Arthur Barstow
Hi All, As I indicated in [1], WebApps already has a relatively large number of specs in progress and the group has agreed to add some new specs. As such, to review any new charter addition proposals, I think we need at least the following: 1. Relatively clear scope of the feature(s). (This

[Bug 15470] New: Changing the selection creates a Range object

2012-01-09 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15470 Summary: Changing the selection creates a Range object Product: WebAppsWG Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: normal Priority:

querySelectorAll() -- selecting _immediate_ children of element

2012-01-09 Thread Marat Tanalin | tanalin . com
querySelector() and querySelectorAll() methods are exciting features, but they do not allow select _immediate_ children of reference element. To address this lack, we could use following syntax: var divs = refElement.querySelectorAll('> DIV'); Here 'divs' variable contains list of DIV eleme

Re: Pressing Enter in contenteditable: or or ?

2012-01-09 Thread Simon Pieters
On Sat, 07 Jan 2012 03:57:33 +0100, Ojan Vafai wrote: BCC: whatwg, CC:public-webapps since discussion of the editing spec has moved I'm OK with this conclusion, but I still strongly prefer "div" to be the "default single-line container name". Why? Also, I'd really like the "default single-