Re: [whatwg] 'datetime-local' and 'datetime' comments

2012-11-21 Thread Mounir Lamouri
On 20/11/12 08:37, Nicolas Froidure wrote: On 20/11/2012 07:17, Ian Hickson wrote: a date/time picker that works just like the one without a timezone, except that it then converts the time you give into UTC. That's exactly the behavior i would like to have. From the server side it seems

Re: [whatwg] 'datetime-local' and 'datetime' comments

2012-11-21 Thread Mounir Lamouri
On 20/11/12 06:17, Ian Hickson wrote: FWIW, the UI I'd expect for today's datetime, maybe renamed to datetime-global, would be a date/time picker that works just like the one without a timezone, except that it then converts the time you give into UTC. So far example, I'm in the PST time

Re: [whatwg] Forms-related feedback

2012-11-21 Thread Mounir Lamouri
On 20/11/12 22:51, Ian Hickson wrote: On Tue, 20 Nov 2012, Mounir Lamouri wrote: Currently stepUp(n) and stepDown(n) are very basic methods. They more or less do value += n * allowedValueStep; with n = -n; if stepDown() was called. In addition of being pretty dumb, there are a lot of

Re: [whatwg] Make stepUp() and stepDown() more developer-friendly

2012-11-21 Thread Mounir Lamouri
On 20/11/12 22:55, Ian Hickson wrote: On Tue, 20 Nov 2012, Scott González wrote: Can you explain why these methods should be no-ops if the value is above the max or below the min? In jQuery UI, we decided that using these methods should always result in a valid value. I actually missed

[whatwg] Provide data chunk with the ProgressEvent

2012-11-21 Thread Nicolas Froidure
I'm currently working on a way to update UI before the all XHR datas to be loaded (sample http://server.elitwork.com/experiments/pagestream/index.html) For that need i used the progress listener http://dvcs.w3.org/hg/progress/raw-file/tip/Overview.html#progressevent but it's particularly

Re: [whatwg] URL: percent-encoded host

2012-11-21 Thread Anne van Kesteren
On Tue, Nov 20, 2012 at 3:38 AM, Boris Zbarsky bzbar...@mit.edu wrote: So I don't think we should require this behavior. Thanks, I went with requiring decoding per UTF-8 for now causing sequences such as %80 to turn into U+FFFD. I think that simplification over just decoding valid utf-8

Re: [whatwg] Provide data chunk with the ProgressEvent

2012-11-21 Thread Anne van Kesteren
On Wed, Nov 21, 2012 at 5:07 PM, Nicolas Froidure froidure_nico...@yahoo.fr wrote: I think it could be more usefull if the progress event was providing a chunk property containing only the new datas loaded. The plan for this is that you set responseType to stream and use the Stream object

Re: [whatwg] Provide data chunk with the ProgressEvent

2012-11-21 Thread Boris Zbarsky
On 11/21/12 11:07 AM, Nicolas Froidure wrote: Indeed, the only way to access to the data chunk loaded is to keep a reference to the previous value of xhr.responseText. Nicolas, see http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/0741.html (implemented in Gecko as the

Re: [whatwg] Provide data chunk with the ProgressEvent

2012-11-21 Thread Anne van Kesteren
On Wed, Nov 21, 2012 at 5:44 PM, Boris Zbarsky bzbar...@mit.edu wrote: Nicolas, see http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/0741.html (implemented in Gecko as the moz-chunked-text and moz-chunked-arraybuffer response types so people can experiment with it). Would that

Re: [whatwg] Improving autocomplete

2012-11-21 Thread Mounir Lamouri
On 11/11/12 13:26, Charles McCathie Nevile wrote: On Sun, 11 Nov 2012 07:50:48 +0100, Maciej Stachowiak m...@apple.com wrote: (1) If this API fills in a form completely based on stored data, and not by completing the user's typing, then it is autofill rather than autocomplete. Yep. (2)

Re: [whatwg] Provide data chunk with the ProgressEvent

2012-11-21 Thread Jussi Kalliokoski
There is something like this cooking in the form of responseType = chunked-text and responseType = chunked-arraybuffer For reference, see [1] and [2]. Would be cool to hear a status update on specifying these. Anyway, apparently the right forum of discussion for this is the webapps mailing list.

[whatwg] URL: query string

2012-11-21 Thread Anne van Kesteren
Writing and parsing currently distinguish between URLs that can be written relatively and those that cannot. URLs with a relative scheme http://url.spec.whatwg.org/#relative-scheme have a relative syntax and the others do not. Fragment makes sense to have on both, although for setting hash (not

Re: [whatwg] URL: IPv6 parsing and model/serializing

2012-11-21 Thread Anne van Kesteren
On Thu, Nov 15, 2012 at 4:02 PM, Boris Zbarsky bzbar...@mit.edu wrote: Just to be clear, I don't necessarily object to normalizing IPv6 addresses. Especially since I'm no longer actively working on networking code, so it's not like it would be work for _me_. I just mentioned the only concern I

Re: [whatwg] Provide data chunk with the ProgressEvent

2012-11-21 Thread Nicolas Froidure
Perfectly ! Thanks. Registered to webapps list too, sorry for the noise. On 21/11/2012 17:44, Boris Zbarsky wrote: On 11/21/12 11:07 AM, Nicolas Froidure wrote: Indeed, the only way to access to the data chunk loaded is to keep a reference to the previous value of xhr.responseText. Nicolas,

Re: [whatwg] Improving autocomplete

2012-11-21 Thread Peter Kasting
On Wed, Nov 21, 2012 at 9:00 AM, Mounir Lamouri mou...@lamouri.fr wrote: I feel like the real use case is when a user wants to make custom with a web site for the first time. It might be indeed harder to get a good transformation ration if the user has to write all those information. However,

Re: [whatwg] URL: query string

2012-11-21 Thread James Ross
(Browser support is all over the map. For mailto:test?test; Firefox gives neither pathname/search, Opera/Safari give pathname/search, Chrome only gives pathname, which is test?test. No access to Internet Explorer unfortunately.) FWIW, according to http://dump.testsuite.org/url/inspect.html,

Re: [whatwg] URL: query string

2012-11-21 Thread Anne van Kesteren
On Wed, Nov 21, 2012 at 9:07 PM, James Ross sil...@warwickcompsoc.co.uk wrote: FWIW, according to http://dump.testsuite.org/url/inspect.html, IE10 gives pathname/search as test/?test in both IE10 and IE9 modes. Sweet, is that true for test:test?test, about:blank?test, and data:test?test too?

Re: [whatwg] URL: query string

2012-11-21 Thread James Ross
On Wed, Nov 21, 2012 at 9:07 PM, James Ross sil...@warwickcompsoc.co.uk wrote: FWIW, according to http://dump.testsuite.org/url/inspect.html, IE10 gives pathname/search as test/?test in both IE10 and IE9 modes. Sweet, is that true for test:test?test, about:blank?test, and

Re: [whatwg] Autocomplete and autofill features and feedback thereon

2012-11-21 Thread Ilya Sherman
On Tue, Nov 20, 2012 at 5:17 PM, Ian Hickson i...@hixie.ch wrote: On Tue, 16 Oct 2012, Ilya Sherman wrote: The payment instrument type is almost certainly appropriate to add -- it is included on almost every website that I've encountered that includes payment card fields. It was an

Re: [whatwg] Improving autocomplete

2012-11-21 Thread Nils Dagsson Moskopp
Peter Kasting pkast...@google.com schrieb am Wed, 21 Nov 2012 12:04:56 -0800: […] On the contrary, as a user I find that case extremely compelling. Maybe I'm too easily frustrated, but it's intensely annoying when I have to fill out all my personal information yet again just because I've

Re: [whatwg] Checkboxes that control other checkboxes

2012-11-21 Thread Ian Hickson
On Sun, 14 Aug 2011, Timo Beermann wrote: It should be able to implemet checkboxes, where by only activating/deactivating this single checkbox you can active/deactivate multiple other checkboxes. That is possible with scripting today, but it should be possible without scripting, only with

Re: [whatwg] Improving autocomplete

2012-11-21 Thread Nils Dagsson Moskopp
Nils Dagsson Moskopp n...@dieweltistgarnichtso.net schrieb am Thu, 22 Nov 2012 02:11:38 +0100: […] The proper solution is to let people vote with their wallet for devices that are perceived as making input easier – not to hand over power to site users making it easier to sniff data.

Re: [whatwg] Improving autocomplete

2012-11-21 Thread Peter Kasting
On Wed, Nov 21, 2012 at 5:11 PM, Nils Dagsson Moskopp n...@dieweltistgarnichtso.net wrote: The proper solution is to let people vote with their wallet for devices that are perceived as making input easier – not to hand over power to site users making it easier to sniff data. This contains

Re: [whatwg] Autocomplete and autofill features and feedback thereon

2012-11-21 Thread Dan Beam
On Wed, Nov 21, 2012 at 3:55 PM, Ilya Sherman isher...@chromium.org wrote: On Tue, Nov 20, 2012 at 5:17 PM, Ian Hickson i...@hixie.ch wrote: On Tue, 16 Oct 2012, Ilya Sherman wrote: The payment instrument type is almost certainly appropriate to add -- it is included on almost every website

Re: [whatwg] restricted palette for input type=color

2012-11-21 Thread Ian Hickson
On Thu, 3 May 2012, Markus Ernst wrote: Am 03.05.2012 00:50 schrieb Ian Hickson: On Mon, 7 Mar 2011, Markus Ernst wrote: A content management or blog system for a corporate website allows to set font and background colors. The designers define allowed color sets the way that the

Re: [whatwg] 'datetime-local' and 'datetime' comments

2012-11-21 Thread Ian Hickson
On Wed, 21 Nov 2012, Mounir Lamouri wrote: On 20/11/12 06:17, Ian Hickson wrote: FWIW, the UI I'd expect for today's datetime, maybe renamed to datetime-global, would be a date/time picker that works just like the one without a timezone, except that it then converts the time you give