Re: Indexed DB: Opening connections, versions, and priority

On Wed, Feb 26, 2014 at 10:35 AM, Joshua Bell wrote: > While looking at a Chrome bug [1], I reviewed the Indexed DB draft, section > 3.3.1 [2] Opening a database: > > "These steps are not run for any other connections with the same origin and > name but with a higher version" > > And the note: "Th

Re: [clipboard events] seeking implementor feedback on using CID: URI scheme for pasting embedded binary data

>> Of course it would be nice to support a script that wants to generate random >> HTML with embedded files >> use case for example with a CANVAS app where the script wants to copy the >> state of the CANVAS > I was thinking about images that aren't available cross-domain Indeed, that's anot

[Bug 24823] [ServiceWorker]: "MAY NOT" is not defined in RFC 2119

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24823 Jungkee Song changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Bug 24848] New: [imports]: ES6 module loader should be aware modules in HTML Imports

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24848 Bug ID: 24848 Summary: [imports]: ES6 module loader should be aware modules in HTML Imports Product: WebAppsWG Version: unspecified Hardware: PC OS: Linux

[Bug 24338] Spec should have Fetch for Blob URLs

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24338 Bug 24338 depends on bug 23147, which changed state. Bug 23147 Summary: Describe File API Model https://www.w3.org/Bugs/Public/show_bug.cgi?id=23147 What|Removed |Added ---

[Bug 24453] Expose interfaces to workers

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24453 Arun changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 23147] Describe File API Model

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23147 Arun changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[Bug 24072] Clarify handling of neutered objects

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24072 Bug 24072 depends on bug 24339, which changed state. Bug 24339 Summary: File API should specify Blob.close() with a state in the model and influence on read methods https://www.w3.org/Bugs/Public/show_bug.cgi?id=24339 What|Remo

[Bug 24470] Link to #networkError in fetching section is broken

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24470 Arun changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 23853] Please clarify the interpretation of the WebIDL undefined Date in the File constructor

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23853 Arun changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[Bug 24102] Specify the targets for events

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24102 Arun changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[Bug 23946] Lift the ban on query parts in “blob:” URIs

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23946 Arun changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[Bug 24469] Definition of "valid blob" is unclear and probably wrong

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24469 Arun changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 24339] File API should specify Blob.close() with a state in the model and influence on read methods

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24339 Arun changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

RE: [clipboard events] seeking implementor feedback on using CID: URI scheme for pasting embedded binary data

> Of course it would be nice to support a script that wants to generate random > HTML with embedded files to place on the clipboard (although I think most of > those use cases can already be met by using URLs and assuming that any > software reading HTML from the clipboard can understand URLs..)

[Bug 24844] New: Spec is missing and elements

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24844 Bug ID: 24844 Summary: Spec is missing and elements Product: WebAppsWG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal

Re: Indexed DB: Opening connections, versions, and priority

On Thu, Feb 27, 2014 at 10:51 AM, Maciej Stachowiak wrote: > > On Feb 26, 2014, at 10:35 AM, Joshua Bell wrote: > > > While looking at a Chrome bug [1], I reviewed the Indexed DB draft, > section 3.3.1 [2] Opening a database: > > > > "These steps are not run for any other connections with the sa

Re: Indexed DB: Opening connections, versions, and priority

On Feb 26, 2014, at 10:35 AM, Joshua Bell wrote: > While looking at a Chrome bug [1], I reviewed the Indexed DB draft, section > 3.3.1 [2] Opening a database: > > "These steps are not run for any other connections with the same origin and > name but with a higher version" > > And the note: "

Re: [admin] Should WebApps' HTML Templates spec be published as a WG Note?

On 2/27/14 11:41 AM, ext Rafael Weinstein wrote: What do you recommend? It seems a little heavy-handed to kill it or gut it. What about putting a big-red warning at the top that it has been merged to HTML and no longer has normative weight. I don't have a strong preference now and would like

Re: [admin] Should WebApps' HTML Templates spec be published as a WG Note?

What do you recommend? It seems a little heavy-handed to kill it or gut it. What about putting a big-red warning at the top that it has been merged to HTML and no longer has normative weight. On Thu, Feb 27, 2014 at 7:27 AM, Arthur Barstow wrote: > On 2/26/14 9:43 AM, ext Arthur Barstow wrote:

Re: [admin] Should WebApps' HTML Templates spec be published as a WG Note?

On 2/26/14 9:43 AM, ext Arthur Barstow wrote: Hi Robin, Dimitri, All, Since HTML Templates is now part of HTML5, to help avoid confusion, I think WebApps' last TR of the spec ([html-templates]) should be replaced with a WG Note that clearly indicates WebApps' work on the standalone spec has s

Re: Publishing a new WD of Clipboard API and events spec

Arthur Barstow wrote: > Given the last WD of Clipboard API was published about one year ago > (April 2013) and the spec has had some substantive changes ([1]), I > think it would be useful to publish a new WD to replace the current > Technical Report and to clearly indicate the spec is active.