Re: [whatwg] @autocomplete sections

2014-05-22 Thread Ian Hickson
On Tue, 13 May 2014, Matthew Noorenberghe wrote: > > While looking at implementing the new autocomplete attribute syntax, I > was wondering about the driver for section-* tokens. The example in the > spec[1] with multiple shipping addresses for one checkout isn't > something I've seen done in

[whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

2014-05-22 Thread Justin Novosad
tl;dr: The color space of canvas backing stores is undefined, which causes problems for many web devs, but also has non-negligible advantages. So be careful what you wish for. I saw some confusion and questions needing answers in the "WebGL and ImageBitmaps" thread regarding color management. I wi

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

2014-05-22 Thread Rik Cabanier
Hi justin, thanks for this explanation! On Thu, May 22, 2014 at 12:21 PM, Justin Novosad wrote: > tl;dr: The color space of canvas backing stores is undefined, which causes > problems for many web devs, but also has non-negligible advantages. So be > careful what you wish for. > > I saw some c

[whatwg] HTTP status code from JavaScript

2014-05-22 Thread Michael Heuberger
Hello WhatWG There is a need to obtain the HTTP status code for the page itself from JavaScript: https://bugzilla.mozilla.org/show_bug.cgi?id=999886 I think this would be a great feature to save additional traffic in an already congested internet. Because I see lots of queries made by XMLHttpRequ

Re: [whatwg] HTTP status code from JavaScript

2014-05-22 Thread James Greene
I'm not opposed to this idea but... what Is a realistic use case for this? Sincerely, James Greene On Thu, May 22, 2014 at 10:36 PM, Michael Heuberger < michael.heuber...@binarykitchen.com> wrote: > Hello WhatWG > > There is a need to obtain the HTTP status code for the page itself from >

Re: [whatwg] HTTP status code from JavaScript

2014-05-22 Thread Michael Heuberger
Hi James Single page apps! These become more and more popular with frameworks like RactiveJS or AngularJS. There the first request is a HTTP request, for any subsequent requests an AJAX one is generated. The problem is the first HTTP request. The framework is unable to detect 404s with the first

Re: [whatwg] HTTP status code from JavaScript

2014-05-22 Thread Julian Reschke
On 2014-05-23 06:53, Michael Heuberger wrote: Hi James Single page apps! These become more and more popular with frameworks like RactiveJS or AngularJS. There the first request is a HTTP request, for any subsequent requests an AJAX one is generated. The problem is the first HTTP AJAX requests

Re: [whatwg] HTTP status code from JavaScript

2014-05-22 Thread Michael Heuberger
Hi Julian Yes, with "AJAX" requests I meant using XMLHTTPRequest. > If the initial page load yields a 404 will there be any scripts to > execute at all? Oh yes, absolutely. Have you ever written a single page app? There is lots of logic to execute when a 404 occurs. I could count plenty of use c