[Bug 10623] Simplify Web IDL exceptions

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10623 Cameron McCormack changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug 10622] ECMAScript binding for exceptions

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10622 Cameron McCormack changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

Re: CfC: new WD of Clipboard API and Events; deadline April 5

On Sun, Apr 10, 2011 at 11:30, Charles McCathieNevile wrote: > comments on a couple of timeless' comments. > > > On Sun, 10 Apr 2011 18:20:35 +0200, timeless wrote: > >> Calling clearData() empties the system clipboard, or removes the specified >>> type of data from the clipboard. See HTML5 for d

RE: publish new Working Draft of Indexed Database API; deadline April 16

On Saturday, April 09, 2011 4:23 AM, Arthur Barstow wrote: > The Editors of the Indexed Database API would like to publish a new > Working Draft of their spec and this is a Call for Consensus to do so: > > http://dvcs.w3.org/hg/IndexedDB/raw-file/tip/Overview.html > > If one agrees with this pr

Re: [FileAPI] FileWriter and read-only files

On 4/11/2011 2:32 PM, Ian Hickson wrote: On Mon, 11 Apr 2011, Glenn Maynard wrote: createWriter method to the objects in the HTMLInputElement.files array (a new subclass of File), to create a writer for the underlying file. That would violate the user expectation that files provided using a fil

Re: [FileAPI] FileWriter and read-only files

On Mon, Apr 11, 2011 at 5:32 PM, Ian Hickson wrote: > > createWriter method to the objects in the HTMLInputElement.files array > > (a new subclass of File), to create a writer for the underlying file. > > That would violate the user expectation that files provided using a file > upload control on

Re: [FileAPI] FileWriter and read-only files

On Mon, 11 Apr 2011, Glenn Maynard wrote: > > createWriter method to the objects in the HTMLInputElement.files array > (a new subclass of File), to create a writer for the underlying file. That would violate the user expectation that files provided using a file upload control on a form can't be

Re: [FileAPI] FileWriter and read-only files

On Mon, Apr 11, 2011 at 4:22 PM, Eric Uhrhane wrote: > Are you thinking of FileEntry? File objects are always immutable, and > there's currently no way to get from a File to a FileWriter. > I'm thinking of File, but I didn't notice that there's no FileWriter(File) constructor. I suppose the an

Re: [FileAPI] FileWriter and read-only files

On Mon, Apr 11, 2011 at 12:16 PM, Glenn Maynard wrote: > File objects should have a "readOnly" property, indicating whether write > permission is granted by the user.  Files returned from elements > should, by default, set it.  Constructing a FileWriter using a File with its > readOnly property s

[FileAPI] FileWriter and read-only files

File objects should have a "readOnly" property, indicating whether write permission is granted by the user. Files returned from elements should, by default, set it. Constructing a FileWriter using a File with its readOnly property set should throw an exception. Later, it would be good to also h

RE: [FileAPI] Result of calling MultipleReads on FileReader

On Monday, April 11, 2011 10:23 AM, Eric Uhrhane wrote: > On Mon, Apr 11, 2011 at 9:33 AM, Arun Ranganathan wrote: > > In general, I'm averse to throwing, since I think it puts an additional > > burden on the developer (to catch, for example). > > I don't think so. I think that calling two read m

Re: [FileAPI] Result of calling MultipleReads on FileReader

On Mon, Apr 11, 2011 at 1:28 PM, Arun Ranganathan wrote: > > > On the main thread, with your proposal, all reads will stop since an > exception has been raised. > > That's odd--why would that happen? Normally one expects an API call that > throws an exception to have no effect. It'd be particul

Re: [FileAPI] Result of calling MultipleReads on FileReader

On 4/11/11 1:04 PM, Glenn Maynard wrote: On Mon, Apr 11, 2011 at 12:33 PM, Arun Ranganathan > wrote: In general, I'm averse to throwing, since I think it puts an additional burden on the developer (to catch, for example). Only if the developer is trying to catc

Re: [FileAPI] Result of calling MultipleReads on FileReader

On Mon, Apr 11, 2011 at 9:05 AM, Adrian Bateman wrote: > On Monday, April 11, 2011 8:28 AM, Arun Ranganathan wrote: >> On 3/31/11 6:12 PM, Eric Uhrhane wrote: >> > I think it's cleaner and simpler just to throw.  FileReader and XHR >> > are already different enough that a bit more, as long as it's

Re: [FileAPI] Result of calling MultipleReads on FileReader

On Mon, Apr 11, 2011 at 12:33 PM, Arun Ranganathan wrote: > In general, I'm averse to throwing, since I think it puts an additional > burden on the developer (to catch, for example). Only if the developer is trying to catch all exceptions, which you usually don't. Most developers don't try to

Re: Offline Web Applications status

2011/4/7 Michael Nordman > > > 2011/4/7 louis-rémi BABE > >> Thank you all for your valuable answers. >> >> There seems to be a pretty solid agreement on "ability to exclude the >> master page form the cache". >> Michael, you are suggesting using a different way of referring to the >> manifest:

Re: [FileAPI] Result of calling MultipleReads on FileReader

On 4/11/11 12:05 PM, Adrian Bateman wrote: On Monday, April 11, 2011 8:28 AM, Arun Ranganathan wrote: On 3/31/11 6:12 PM, Eric Uhrhane wrote: I think it's cleaner and simpler just to throw. FileReader and XHR are already different enough that a bit more, as long as it's a usability improvement

Re: [FileAPI] Seeking status and plan

On Apr/11/2011 11:20 AM, ext Arun Ranganathan wrote: On 4/11/11 9:38 AM, Arthur Barstow wrote: Hi Arun, Jonas - what is the status/plan for the File API spec? What remains to be done before the spec is "LC ready"? Art: A few things need to be done: 1. There continue to be a few spec. nits a

RE: [FileAPI] Result of calling MultipleReads on FileReader

On Monday, April 11, 2011 8:28 AM, Arun Ranganathan wrote: > On 3/31/11 6:12 PM, Eric Uhrhane wrote: > > I think it's cleaner and simpler just to throw. FileReader and XHR > > are already different enough that a bit more, as long as it's a > > usability improvement, isn't a big deal. The efficien

Re: Support for matchesSelector()

On 2011-04-10 13:32, Lachlan Hunt wrote: On 2011-04-08 16:41, Boris Zbarsky wrote: On 4/8/11 6:44 AM, Lachlan Hunt wrote: We are thinking that implementing with a prefix as Element.oMatchesSelector() is unnecessary After taking Boris' feedback into account, we decided that we'll keep the pre

Re: [FileAPI] Result of calling MultipleReads on FileReader

On 3/31/11 6:12 PM, Eric Uhrhane wrote: On Thu, Mar 31, 2011 at 2:55 PM, Adrian Bateman wrote: On Thursday, March 31, 2011 10:19 AM, Arun Ranganathan wrote: On 3/30/11 2:01 PM, Eric Uhrhane wrote: On Mon, Mar 28, 2011 at 5:37 PM, Adrian Bateman wrote: Is there a reason for the current spec

Re: [FileAPI] Seeking status and plan

On 4/11/11 9:38 AM, Arthur Barstow wrote: Hi Arun, Jonas - what is the status/plan for the File API spec? What remains to be done before the spec is "LC ready"? Art: A few things need to be done: 1. There continue to be a few spec. nits about multiple read calls; these have to be addressed.

[FileAPI] Seeking status and plan

Hi Arun, Jonas - what is the status/plan for the File API spec? What remains to be done before the spec is "LC ready"? (Tracker shows 0 bugs and WebApps does not have a Bugzilla component for this spec). -Thanks, AB