[whatwg] Idea for having InputXML Or ClickXML for HTML5+

2011-02-28 Thread Narendra Sisodiya
We can record mouse and keyboard activity in xml. There are many events which are resolution independent. for example mouse clicks, button press events . Now suppose you are dealing with some animation or game or just a slideshow. what you do ? you type some buttons from mouse or keyboard. Now if y

Re: [whatwg] Can we deprecate alert(), confirm(), prompt() ?

2011-02-28 Thread Ojan Vafai
FWIW, chromium is planning on experimenting with disallowing modal dialogs during the beforeunload/unload events. http://code.google.com/p/chromium/issues/detail?id=68780 On Tue, Mar 1, 2011 at 11:57 AM, Tab Atkins Jr. wrote: > On Mon, Feb 28, 2011 at 4:49 PM, Peter Kasting > wrote: > > On Mon,

Re: [whatwg] Can we deprecate alert(), confirm(), prompt() ?

2011-02-28 Thread Tab Atkins Jr.
On Mon, Feb 28, 2011 at 4:49 PM, Peter Kasting wrote: > On Mon, Feb 28, 2011 at 4:42 PM, Ian Hickson wrote: > >> > 2. if we are still keeping them, can we disable them in >> > onbeforeunload/onunload[/onhide] etc. Many sites add extra dialogs in >> > those events to confuse users, so that they ca

Re: [whatwg] Can we deprecate alert(), confirm(), prompt() ?

2011-02-28 Thread Peter Kasting
On Mon, Feb 28, 2011 at 4:42 PM, Ian Hickson wrote: > > 2. if we are still keeping them, can we disable them in > > onbeforeunload/onunload[/onhide] etc. Many sites add extra dialogs in > > those events to confuse users, so that they can trap users for little > > longer. > > That's not a bad idea

Re: [whatwg] Can we deprecate alert(), confirm(), prompt() ?

2011-02-28 Thread Ian Hickson
On Thu, 25 Nov 2010, Biju wrote: > > 1. Can we deprecate alert(), confirm(), prompt() ? > At present many web2.0 js libs are providing alternate [and cool > looking] methods to achieve use cases where we need to use alert(), > confirm(), prompt(). So do we need those modal dialogs any longer? Well

Re: [whatwg] Intent of the FileSystem API

2011-02-28 Thread Glenn Maynard
On Mon, Feb 28, 2011 at 7:10 PM, Eric Uhrhane wrote: > Our current implementation on Windows uses the standard API calls that > limit paths to 256 characters long. If your profile directory is > deeply nested [e.g. because you have a really long username], code > Worse, the profile directory is

Re: [whatwg] Intent of the FileSystem API

2011-02-28 Thread Eric Uhrhane
On Mon, Feb 28, 2011 at 2:54 PM, Charles Pritchard wrote: > I'd like some clarification on the intent of the FileSystem API: > requestFileSystem permanent, getDirectory and getFile. The FileSystem API has several goals. Some of them are targeted by the current spec, and some have been discussed,

Re: [whatwg] Microphone Device API

2011-02-28 Thread Aryeh Gregor
On Mon, Feb 28, 2011 at 9:55 AM, Bjartur Thorlacius wrote: > Would POSIX sh suffice for your purposes? > The simplest solution I can think of is using sh pipes and standardized > device names. POSIX sh is immensely complicated, is not specified to anywhere near the precision needed by web standar

Re: [whatwg] Intent of the FileSystem API

2011-02-28 Thread Ian Hickson
On Mon, 28 Feb 2011, Charles Pritchard wrote: > > I'd like some clarification on the intent of the FileSystem API: > requestFileSystem permanent, getDirectory and getFile. > > Are they intended to directly pass through to the host operating system, or > are they just programming constructs? > > T

[whatwg] Intent of the FileSystem API

2011-02-28 Thread Charles Pritchard
I'd like some clarification on the intent of the FileSystem API: requestFileSystem permanent, getDirectory and getFile. Are they intended to directly pass through to the host operating system, or are they just programming constructs? They're not particularly easy to use, compared to the Index

Re: [whatwg] Microphone Device API

2011-02-28 Thread Silvia Pfeiffer
On Tue, Mar 1, 2011 at 1:35 AM, Bjartur Thorlacius wrote: > On 2/28/11, Harald Alvestrand wrote: >> - Let users control access to microphone (whether my app can reach it or >> not) >> - Let users turn off and on their microphone >> > Seems to be out of HTML's scope. I don't think that's true. I

Re: [whatwg] 7.3 Timers

2011-02-28 Thread Boris Zbarsky
On 2/28/11 2:13 PM, Alexandre Morgaut wrote: When I read: Any arguments are passed straight through to the handler. I wonder if it does not mean that I should pass one parameter per argument to pass to the handler -> setTimeout( myhandler, 1000, arg1, arg2, arg3); Yes. But well, the signatu

[whatwg] 7.3 Timers

2011-02-28 Thread Alexandre Morgaut
Here some Proposals / Features requests Any comment would be welcome http://www.whatwg.org/specs/web-apps/current-work/multipage/timers.html 1) arguments I think that "args", the third parameter of setTimeout & setInterval is not enough described Should arguments be an Array, or any "Array l

Re: [whatwg] wrapper element

2011-02-28 Thread Tab Atkins Jr.
On Mon, Feb 28, 2011 at 10:46 AM, usuario wrote: >> carries no semantic meaning.  If you are using it for such, the >> semantic is purely internal to your application, and thus doesn't >> carry the common meaning of "semantics" as used on the web. > > We have no problems with definition. But i

Re: [whatwg] wrapper element

2011-02-28 Thread Ashley Sheridan
On Mon, 2011-02-28 at 18:46 +, usuario wrote: > [Had problems sending my mails to the list, resending message] > > Some of you may be questioning why a wrapper element if it has not > semantics, the thing is, It DO have semantics. > > Wrapper: > a container element whose solely purpose is to

Re: [whatwg] wrapper element

2011-02-28 Thread usuario
[Had problems sending my mails to the list, resending message] Some of you may be questioning why a wrapper element if it has not semantics, the thing is, It DO have semantics. Wrapper: a container element whose solely purpose is to isolate flow content for visually appealing purposes. It it usua

Re: [whatwg] Optional non-blocking mode for simple dialogs (alert, confirm, prompt).

2011-02-28 Thread Bjartur Thorlacius
On 2/27/11, Justin Dolske wrote: > But more generally, I wonder if it's worth bothering with now... It's > pretty common for web pages to just implement their own custom > in-content dialogs (floating divs, really), which they have far greater > control over. And starting with Firefox 4, we're mak

Re: [whatwg] wrapper element

2011-02-28 Thread Tab Atkins Jr.
On Sun, Feb 27, 2011 at 12:46 PM, Jukka K. Korpela wrote: > Bjartur Thorlacius wrote: > [quotation reorganized by me] >> What semantics would such an wrapper element provide over ? I'd >> rather discourage, and provide alternative features to wrapping. >> Providing another element for that purpose

Re: [whatwg] Microphone Device API

2011-02-28 Thread Harald Alvestrand
On 02/28/11 16:10, Bjartur Thorlacius wrote: On 2/28/11, Harald Alvestrand wrote: On 02/28/11 15:55, Bjartur Thorlacius wrote: On 2/28/11, Harald Alvestrand wrote: On 02/28/11 15:35, Bjartur Thorlacius wrote: In effect, you want to create pipelines in JS/ES? I need pipelines that can be

Re: [whatwg] Microphone Device API

2011-02-28 Thread Bjartur Thorlacius
On 2/28/11, Harald Alvestrand wrote: > On 02/28/11 15:55, Bjartur Thorlacius wrote: >> On 2/28/11, Harald Alvestrand wrote: >>> On 02/28/11 15:35, Bjartur Thorlacius wrote: In effect, you want to create pipelines in JS/ES? >>> I need pipelines that can be manipulated from Javascript, ye

Re: [whatwg] Microphone Device API

2011-02-28 Thread Harald Alvestrand
On 02/28/11 15:55, Bjartur Thorlacius wrote: On 2/28/11, Harald Alvestrand wrote: On 02/28/11 15:35, Bjartur Thorlacius wrote: In effect, you want to create pipelines in JS/ES? I need pipelines that can be manipulated from Javascript, yes. Javascript is not a millisecond-precise language; th

Re: [whatwg] Microphone Device API

2011-02-28 Thread Bjartur Thorlacius
On 2/28/11, Harald Alvestrand wrote: > On 02/28/11 15:35, Bjartur Thorlacius wrote: >>> >> In effect, you want to create pipelines in JS/ES? >> > I need pipelines that can be manipulated from Javascript, yes. > Javascript is not a millisecond-precise language; the running of the > pipelines has to

Re: [whatwg] Microphone Device API

2011-02-28 Thread Harald Alvestrand
On 02/28/11 15:35, Bjartur Thorlacius wrote: On 2/28/11, Harald Alvestrand wrote: - Let users control access to microphone (whether my app can reach it or not) - Let users turn off and on their microphone Seems to be out of HTML's scope. I would very much want to avoid having the "record to

Re: [whatwg] Microphone Device API

2011-02-28 Thread Bjartur Thorlacius
On 2/28/11, Harald Alvestrand wrote: > - Let users control access to microphone (whether my app can reach it or > not) > - Let users turn off and on their microphone > Seems to be out of HTML's scope. > I would very much want to avoid having the "record to file/buffer" be a > fundamental part of

Re: [whatwg] Microphone Device API

2011-02-28 Thread Harald Alvestrand
On 02/17/11 10:30, Jörn Zaefferer wrote: Hi, here at SoundCloud we're interested in an API for recording in the browser ( http://blog.soundcloud.com/2010/12/01/record/ ), without Flash and even on mobile browsers. The get things moving with the current idea of a device API ( http://www.whatwg.or

Re: [whatwg] wrapper element

2011-02-28 Thread Diogo Resende
I agree with Bjartur, does the work fine. On Sun, 27 Feb 2011 19:40:15 -0500, ddailey wrote: Given that SVG and HTML are now interminglable in the same document, why not start intermingling their tag definitions? Please don't start mixing SVG+HTML properties or one day it will be a hell of