Re: [whatwg] Inconsistent behavior for empty-string URLs

2009-12-16 Thread Simon Pieters
On Wed, 16 Dec 2009 02:21:33 +0100, Jonas Sicking jo...@sicking.cc wrote: On Tue, Dec 15, 2009 at 4:11 PM, Nicholas Zakas nza...@yahoo-inc.com wrote: Here's what I would propose: 1. Empty string attributes for HTML elements specifying resources to automatically download are considered

[whatwg] Web API for speech recognition and synthesis

2009-12-16 Thread Deborah Dahl
(resending to include the whatwg list, sorry for multiple postings) Hi Olli, Thank you for bringing this interesting thread to the Multimodal Interaction Working Group's attention. The working group is in fact very active. Although it is chartered as W3C Member-only, we do have a public mailing

Re: [whatwg] Inconsistent behavior for empty-string URLs

2009-12-16 Thread Jonas Sicking
On Wed, Dec 16, 2009 at 2:59 AM, Simon Pieters sim...@opera.com wrote: On Wed, 16 Dec 2009 02:21:33 +0100, Jonas Sicking jo...@sicking.cc wrote: On Tue, Dec 15, 2009 at 4:11 PM, Nicholas Zakas nza...@yahoo-inc.com wrote: Here's what I would propose: 1. Empty string attributes for HTML

[whatwg] Passing more than JSON data to workers

2009-12-16 Thread Jan Fabry
Hello, Has it been considered to pass more than JSON data to workers? I could not find a rationale behind this in the FAQ, or in other places I looked. I understand the need for separation because of concurrency issues, but aren't there other ways to accomplish this? (The following text was

Re: [whatwg] Passing more than JSON data to workers

2009-12-16 Thread Simon Pieters
On Wed, 16 Dec 2009 18:26:59 +0100, Boris Zbarsky bzbar...@mit.edu wrote: On 12/16/09 9:23 AM, Jan Fabry wrote: The Google Gears API seems to provide both createWorker(scriptText) and createWorkerFromUrl(scriptUrl). Why was only the URL variant retained in the Web Workers spec? Does using

Re: [whatwg] Inconsistent behavior for empty-string URLs

2009-12-16 Thread Nicholas Zakas
Looks like a good list to me. -Nicholas __ Commander Lock: Damnit Morpheus, not everyone believes what you believe! Morpheus: My beliefs do not require them to. -Original Message- From: Jonas Sicking [mailto:jo...@sicking.cc] Sent:

Re: [whatwg] Passing more than JSON data to workers

2009-12-16 Thread Drew Wilson
I'm not certain what a deep copy of the function means - would you need to copy the entire lexical scope of the function? For example, let's say you do this: var foo = 1; function setFoo(val) { foo = val; } function getFoo() { return foo; } worker.postMessage(setFoo);

Re: [whatwg] Passing more than JSON data to workers

2009-12-16 Thread Jonathan 'J5' Cook
Simon Pieters wrote: On Wed, 16 Dec 2009 18:26:59 +0100, Boris Zbarsky bzbar...@mit.edu wrote: On 12/16/09 9:23 AM, Jan Fabry wrote: The Google Gears API seems to provide both createWorker(scriptText) and createWorkerFromUrl(scriptUrl). Why was only the URL variant retained in the Web

[whatwg] Question about pushState

2009-12-16 Thread Darin Fisher
[Apologies if this has been discussed before, but I couldn't find it in the archives.] Why does pushState only prune forward session history entries corresponding to the same document? I would have expected it to behave like a reference fragment navigation, which prunes *all* forward session

Re: [whatwg] Question about pushState

2009-12-16 Thread Jonas Sicking
On Wed, Dec 16, 2009 at 11:51 AM, Darin Fisher da...@chromium.org wrote: [Apologies if this has been discussed before, but I couldn't find it in the archives.] Why does pushState only prune forward session history entries corresponding to the same document?  I would have expected it to behave

Re: [whatwg] Question about pushState

2009-12-16 Thread Darin Fisher
On Wed, Dec 16, 2009 at 12:06 PM, Jonas Sicking jo...@sicking.cc wrote: On Wed, Dec 16, 2009 at 11:51 AM, Darin Fisher da...@chromium.org wrote: [Apologies if this has been discussed before, but I couldn't find it in the archives.] Why does pushState only prune forward session history

[whatwg] [ApplicationCache] Clarify When Events Fire

2009-12-16 Thread Joseph Pecoraro
I'd like some clarification on exactly when the ApplicationCache events should fire. Specifically the events that are likely to fire early, such as the checking or downloading events. In 6.9.4 Downloading or updating an application cache, the specification currently says the following for the

Re: [whatwg] Question about pushState

2009-12-16 Thread Jonathan 'J5' Cook
Jonas Sicking wrote: On Wed, Dec 16, 2009 at 11:51 AM, Darin Fisher da...@chromium.org wrote: [Apologies if this has been discussed before, but I couldn't find it in the archives.] Why does pushState only prune forward session history entries corresponding to the same document? I would have

Re: [whatwg] Passing more than JSON data to workers

2009-12-16 Thread Jan Fabry
On 16 Dec 2009, at 19:33, Drew Wilson wrote: I'm not certain what a deep copy of the function means - would you need to copy the entire lexical scope of the function? For example, let's say you do this: var foo = 1; function setFoo(val) { foo = val; } function getFoo() { return foo; }

Re: [whatwg] Passing more than JSON data to workers

2009-12-16 Thread Boris Zbarsky
On 12/16/09 1:27 PM, Jan Fabry wrote: function setFoo(val) { foo = val; } function getFoo() { return foo; } ... After the second postMessage, the worker receives a new object, also a function, bound to a variable with the value 1. What if getFoo were: function getFoo() { return

[whatwg] api for fullscreen()

2009-12-16 Thread Michael Dale
It would be really nice if the html5 spec supported a javascript call to set a target window to fullscreen. The browser would then issue a security warning at the top of the page (similar to pop-ups) and then the user could grant that domain permission to go full-screen. This is especially

Re: [whatwg] api for fullscreen()

2009-12-16 Thread Ian Hickson
On Wed, 16 Dec 2009, Michael Dale wrote: It would be really nice if the html5 spec supported a javascript call to set a target window to fullscreen. The browser would then issue a security warning at the top of the page (similar to pop-ups) and then the user could grant that domain

Re: [whatwg] Question about pushState

2009-12-16 Thread Justin Lebar
On Wed, Dec 16, 2009 at 3:06 PM, Jonas Sicking jo...@sicking.cc wrote: On Wed, Dec 16, 2009 at 11:51 AM, Darin Fisher da...@chromium.org wrote: I would have expected it to behave like a reference fragment navigation, which prunes *all* forward session history entries. I agree. I *think* what

Re: [whatwg] api for fullscreen()

2009-12-16 Thread narendra sisodiya
On Thu, Dec 17, 2009 at 11:42 AM, Ian Hickson i...@hixie.ch wrote: On Wed, 16 Dec 2009, Michael Dale wrote: It would be really nice if the html5 spec supported a javascript call to set a target window to fullscreen. The browser would then issue a security warning at the top of the page

Re: [whatwg] api for fullscreen()

2009-12-16 Thread イアンフェッティ
I think what I've heard from application developers over and over again is that, while the UA may provide some way to go into full screen from in the browser chrome, it is much more discoverable when that capability exists from within the content area (e.g. people are used to clicking on the full

Re: [whatwg] Question about pushState

2009-12-16 Thread Jonas Sicking
On Wed, Dec 16, 2009 at 10:25 PM, Justin Lebar justin.le...@gmail.com wrote: On Wed, Dec 16, 2009 at 3:06 PM, Jonas Sicking jo...@sicking.cc wrote: On Wed, Dec 16, 2009 at 11:51 AM, Darin Fisher da...@chromium.org wrote: I would have expected it to behave like a reference fragment navigation,

Re: [whatwg] api for fullscreen()

2009-12-16 Thread Jonas Sicking
2009/12/16 Ian Fette (イアンフェッティ) ife...@google.com: I think what I've heard from application developers over and over again is that, while the UA may provide some way to go into full screen from in the browser chrome, it is much more discoverable when that capability exists from within the

Re: [whatwg] api for fullscreen()

2009-12-16 Thread イアンフェッティ
2009/12/16 Jonas Sicking jo...@sicking.cc 2009/12/16 Ian Fette (イアンフェッティ) ife...@google.com: I think what I've heard from application developers over and over again is that, while the UA may provide some way to go into full screen from in the browser chrome, it is much more discoverable

Re: [whatwg] api for fullscreen()

2009-12-16 Thread Jonas Sicking
2009/12/16 Ian Fette (イアンフェッティ) ife...@google.com: 2009/12/16 Jonas Sicking jo...@sicking.cc 2009/12/16 Ian Fette (イアンフェッティ) ife...@google.com: I think what I've heard from application developers over and over again is that, while the UA may provide some way to go into full screen from in

Re: [whatwg] api for fullscreen()

2009-12-16 Thread イアンフェッティ
2009/12/16 Jonas Sicking jo...@sicking.cc 2009/12/16 Ian Fette (イアンフェッティ) ife...@google.com: 2009/12/16 Jonas Sicking jo...@sicking.cc 2009/12/16 Ian Fette (イアンフェッティ) ife...@google.com: I think what I've heard from application developers over and over again is that, while the UA

Re: [whatwg] api for fullscreen()

2009-12-16 Thread Robert O'Callahan
2009/12/17 Ian Fette (イアンフェッティ) ife...@google.com I think what I've heard from application developers over and over again is that, while the UA may provide some way to go into full screen from in the browser chrome, it is much more discoverable when that capability exists from within the

Re: [whatwg] api for fullscreen()

2009-12-16 Thread イアンフェッティ
2009/12/16 Robert O'Callahan rob...@ocallahan.org 2009/12/17 Ian Fette (イアンフェッティ) ife...@google.com I think what I've heard from application developers over and over again is that, while the UA may provide some way to go into full screen from in the browser chrome, it is much more