Re: [XHR] request error distinction: abort and error

On Fri, Aug 16, 2013 at 10:40 AM, Hallvord Steen wrote: > > However, what one might want to do is to re-schedule some request and try > again later. In this respect, I think a user cancellation is much closer to a > network error than an abort() call. If the network fails, you can assume it's >

Re: [XHR] request error distinction: abort and error

On Sat, Aug 17, 2013 at 2:40 AM, Hallvord Steen wrote: > > > -> If the request cancellation is trigger by the end user > >This is an abort error. > > Note: The request cancellations by the end user include clicking > > on a stop button in browser chrome, hitting escape, page navigation, etc.

[ime-api] Re: FYI: new WD of Input Method Editor API published

On Aug 16, 2013, at 5:44 AM, Arthur Barstow wrote: > You may recall WebApps and PFWG discussed WebApps' Input Method Editor API > last April ([Mins]). As such, I wanted to let you know a new WD of that spec > was published on August 15: > > If y

Re: [webappsec + webapps] CORS to PR plans

Based on the feedback received during the Call for Consensus, I've updated the draft CORS PR at: http://webappsec-test.info/~bhill2/pub/CORS/index.html Language about an implementation report has been removed, and the only substantive modification from the previous proposed draft is that referenc

Re: Updating Quota API: Promise, Events and some more

On Fri, Aug 16, 2013 at 6:56 AM, Kinuko Yasuda wrote: I had a few bike-sheddy comments as well. > Now the new draft looks like: > > enum StorageType { "temporary", "persistent" }; > > partial interface Navigator { > readonly attribute StorageQuota storageQuota; > }; > > [NoInterfaceOb

Re: [XHR] request error distinction: abort and error

> -> If the request cancellation is trigger by the end user >This is an abort error. > Note: The request cancellations by the end user include clicking > on a stop button in browser chrome, hitting escape, page navigation, etc. > > WDYT? I think the real reason for the disagreement is that th

[XHR] request error distinction: abort and error

Hi, I would like to bring this topic back in the list: [XHR] remove "user cancels request" [1]. It was quite a controversial topic and as far as I recall the discussion was not clearly concluded. We've had three different error cases to distinguish: (A) Network initiated errors (B) abort() call (

Re: Supporting Portrait-First and Landscape-First devices in HTML5 Device Orientation

On Fri, Aug 16, 2013 at 2:11 AM, Lars Knudsen wrote: > Hi, > > I know, I've mentioned this before - but why don't we just define one > (hardware) direction as "0 degrees" (e.g. "portrait up"), align all the > orientation specs and keep things simple for everyone? > > ref > http://lists.w3.org/Arch

Re: Updating Quota API: Promise, Events and some more

On Fri, Aug 16, 2013 at 3:25 AM, Jonas Sicking wrote: > On Thu, Aug 15, 2013 at 9:44 AM, Kinuko Yasuda > wrote: > >> requestQuota for temporary storage: > >> I'd like to better understand the use case for requestQuota for > temporary > >> storage. Are implementations allowed to bring up a prompt

CfC: publish LCWD of File API; deadline August 23

Arun proposed (see below) WebApps publish a Last Call Working Draft of File API and this is a Call for Consensus to do so, using the following ED as the basis: This CfC satisfies the group's requirement to "record the group's decision to request advanc

Re: Supporting Portrait-First and Landscape-First devices in HTML5 Device Orientation

Hi, I know, I've mentioned this before - but why don't we just define one (hardware) direction as "0 degrees" (e.g. "portrait up"), align all the orientation specs and keep things simple for everyone? ref http://lists.w3.org/Archives/Public/public-webapps/2013AprJun/0063.html br Lars On Fr