Re: Seeking agenda items for WebApps' Nov 1-2 f2f meeting

On Mon, Sep 20, 2010 at 6:03 PM, Cameron McCormack wrote: > Art, > > Arthur Barstow: > > * Web IDL - Cameron - will you attend this meeting? > > At this stage I won’t be attending. I believe list discussion should be > sufficient for progressing the spec at this point, and a scheduling > conflic

[Bug 10420] Can you post sample of cross domain for web workers?

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10420 Ian 'Hixie' Hickson changed: What|Removed |Added Status|NEW |RESOLVED CC|

Re: A URL API

On Wed, Sep 22, 2010 at 12:54 AM, Devdatta Akhawe wrote: >> 2) I've added two flavors of appendParameter.  The first flavor takes >> a DOMString for a value and appends a single parameter.  The second >> flavor takes an array of DOMStrings and appends one parameter for each >> array.  This seemed

Re: A URL API

> If you really don't want to care what happened before, either do a > clearParameter every time first, or define your own setParameter that > just clears then appends.  Append/clear is a cleaner API design in > general imo, precisely because you don't have to worry about colliding > with previous

Re: [XHR2] ArrayBuffer integration

On Fri, Sep 24, 2010 at 5:36 PM, Jian Li wrote: > I plan to add ArrayBuffer support to BlobBuilder and FileReader. Chris, it > is good that you would pick up the work for XHR. We can talk about how we're > going to add ArrayBufferView to read ArrayBuffer. All of the Typed Array view types (Uint8A

Re: [XHR2] ArrayBuffer integration

I plan to add ArrayBuffer support to BlobBuilder and FileReader. Chris, it is good that you would pick up the work for XHR. We can talk about how we're going to add ArrayBufferView to read ArrayBuffer. Jian On Fri, Sep 24, 2010 at 5:23 PM, Kenneth Russell wrote: > On Thu, Sep 23, 2010 at 2:42 A

Re: [XHR2] ArrayBuffer integration

On Thu, Sep 23, 2010 at 2:42 AM, Anne van Kesteren wrote: > On Wed, 08 Sep 2010 19:55:33 +0200, Kenneth Russell wrote: >> >> Mozilla's experimental name is "mozResponseArrayBuffer", so perhaps to >> avoid collisions the spec could call it responseArrayBuffer. > > While I do not think there would

Re: Small tweak to FileWriter's event sequences

On Fri, Sep 24, 2010 at 1:15 PM, Eric Uhrhane wrote: > The abort sequence in FileWriter looks like this: > > "If readyState is DONE, throw a FileException with error code > INVALID_STATE_ERR and terminate this overall series of steps. > Set readyState to DONE. > Terminate any steps having to do wi

[Bug 10734] New: Create LR Grammar

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10734 Summary: Create LR Grammar Product: WebAppsWG Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component:

Re: [cors] Case-sensitive matching of origin URLs?

On Fri, Sep 24, 2010 at 12:41 AM, Anne van Kesteren wrote: > On Thu, 23 Sep 2010 08:40:42 +0200, Vladimir Dzhuvinov > wrote: >> >> The CORS draft on the other hand requires case-sensitive matching of >> origins: >> >> http://www.w3.org/TR/access-control/#resource-requests > > It requires case-sen

Small tweak to FileWriter's event sequences

The abort sequence in FileWriter looks like this: "If readyState is DONE, throw a FileException with error code INVALID_STATE_ERR and terminate this overall series of steps. Set readyState to DONE. Terminate any steps having to do with writing a file. Dispatch a progress event called error. Set th

Re: [IndexedDB] A "versionchangeblocked" event

On Fri, Sep 24, 2010 at 3:17 AM, Jeremy Orlow wrote: > Are we really sure this is needed? > I was just writing up a bug for this and started to wonder if we needed any > event when there no longer is a block.  I then realized that once you're > unblocked the onsuccess should fire immediately, so t

Re: Request for Comments: view-mode Media Feature test cases

I was looking at the spec, and it has "minimized" spelled two different ways: minimized Describes a Web application docked or otherwise minimised... On Sep 24, 2010, at 8:47 AM, Arthur Barstow wrote: > > Hi All, > > Opera's participants in the WebApps WG have completed a test suite for the >

Re: [DOMCore] Attr

11.09.2010, в 21:17, Michael A. Puls II написал(а): > At the time, I made > to test some things with Attr nodes. (Note that the description on that page > is outdated.) A few days ago, I fixed some aspects of Attr behavior in WebKit, her

[CORS] Access-Control-Expose-Headers

Regarding the CORS spec: Shouldn't "list of exposed headers" be added to the resource policy bullet list? Or is that already covered by "list of supported headers"? http://www.w3.org/TR/access-control/#resource-processing-model -- Vladimir Dzhuvinov :: software.dzhuvinov.com

[Bug 9989] Is the number of replacement characters supposed to be well-defined? If not this should be explicitly noted. If it is then more detail is required.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9989 Ian 'Hixie' Hickson changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

Re: [CORS] Multiple origin values?

On Fri, 24 Sep 2010 16:31:52 +0200, Vladimir Dzhuvinov wrote: Another question regarding the CORS spec: 1. Why would a browser report multiple Origins to the web server? Redirects. 2. http://www.w3.org/TR/access-control/#resource-requests Why does the spec prescribe "match any" instead o

Re: [IndexedDB] A "versionchangeblocked" event

The strategy we decided on was to send a 'versionchange' event to every database that isn't closed first. Then we loop again and if there are any left that are not closed we fire the blocked event. Since we expect pages to call close() inside their 'versionchange' handler we shouldn't be firing the

[CORS] Multiple origin values?

Another question regarding the CORS spec: 1. Why would a browser report multiple Origins to the web server? 2. http://www.w3.org/TR/access-control/#resource-requests Why does the spec prescribe "match any" instead of "match all" when multiple origin values are received? Shouldn't the server app

Re: [cors] Case-sensitive matching of origin URLs?

>> The CORS draft on the other hand requires case-sensitive matching of >> origins: >> >> http://www.w3.org/TR/access-control/#resource-requests > > It requires case-sensitive matching of the serialization of origins. They > are never parsed into origins to begin with. Does this mean that the valu

Re: [IndexedDB] A "versionchangeblocked" event

Are we really sure this is needed? I was just writing up a bug for this and started to wonder if we needed any event when there no longer is a block. I then realized that once you're unblocked the onsuccess should fire immediately, so there's no need. But wait...isn't this true of normal blockin

Re: [cors] Case-sensitive matching of origin URLs?

On Thu, 23 Sep 2010 08:40:42 +0200, Vladimir Dzhuvinov wrote: The CORS draft on the other hand requires case-sensitive matching of origins: http://www.w3.org/TR/access-control/#resource-requests It requires case-sensitive matching of the serialization of origins. They are never parsed in

[cors] Case-sensitive matching of origin URLs?

Hi, I'm writing a generic Java servlet filter to implement the current CORS draft. I'm confused about the correct way to check if a reported Origin is allowed by the resource's allow list. The Origin spec, which the CORS draft refers to, implies that 2 origins are equal if they match, regardless