[Bug 21836] New: Remove NotSupportedError on creating index for multiEntry index with array keyPath

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21836 Bug ID: 21836 Summary: Remove NotSupportedError on creating index for multiEntry index with array keyPath Classification: Unclassified Product: WebAppsWG Version: unspecified

[Bug 21833] New: Under read* chaining during load event loadends should be suppressed

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21833 Bug ID: 21833 Summary: Under read* chaining during load event loadends should be suppressed Classification: Unclassified Product: WebAppsWG Version: unspecified Hardw

Re: [Shadow DOM] Simplifying level 1 of Shadow DOM

Hello, This is an interesting suggestion. Here are some notes: Reducing to one insertion point doesn't, in itself, eliminate >> distribution, getDistributedNodes(), etc >> I assume you mean "one insertion point that always selects everything". Also, fwiw, >> we use for inheritance. And >

[Shadow DOM] Simplifying level 1 of Shadow DOM

(Resent from correct email address) Hi, First off, thanks to Dimitri and others for all the great work on Shadow DOM and the other pieces of Web Components. While I'm very enthusiastic about Shadow DOM in the abstract, I think things have gotten really complex, and I'd like to seriously propose t

Re: URL comparison

On Thu, Apr 25, 2013 at 11:41 AM, wrote: >> Requests I've heard before I looked at :local-link(): >> >> * Simple equality >> * Ignore fragment >> * Ignore fragment and query >> * Further normalization (browsers don't normalize as much as they >> could during parsing, but maybe this should be an o

RE: URL comparison

> Requests I've heard before I looked at :local-link(): >  > * Simple equality > * Ignore fragment > * Ignore fragment and query > * Further normalization (browsers don't normalize as much as they > could during parsing, but maybe this should be an operation to modify > the URL object rather than

Re: URL comparison

On Thu, Apr 25, 2013 at 4:34 AM, Anne van Kesteren wrote: > Background reading: http://dev.w3.org/csswg/selectors/#local-pseudo > and http://url.spec.whatwg.org/ > > :local-link() seems like a special case API for doing URL comparison > within the context of selectors. It seems like a great featur

Re: Why not be multiEntry and array keyPath togather?

Some of us were just discussing this yesterday - it does seem reasonable for the next iteration. Can you file a bug at https://www.w3.org/ (product: WebAppsWG, component: Indexed Database API) to track this? Including scenario details such as you've done above would be great. On Thu, Apr 25, 20

Proposal for a filesystem API

Hi WebApps! There has been a lot of controversy about implementing a file system API in other browsers. Firefox and IE already support storing files in IndexedDB, but it seems that web developers need something simpler in some cases and there's also the filesystem URL scheme that is not covered by

Re: Fixing appcache: a proposal to get us started

On 2013-03-27 01:20, Jonas Sicking wrote: On Tue, Mar 26, 2013 at 1:48 AM, James Graham wrote: On 03/26/2013 08:02 AM, Jonas Sicking wrote: Another "feature" that we are proposing is to drop the current manifest format and instead use a JSON based one. The most simple reason for this is that

Re: Collecting real world use cases (Was: Fixing appcache: a proposal to get us started)

On 19.04.13 00:01, "Charles McCathie Nevile" wrote: >On Thu, 18 Apr 2013 19:19:17 +0300, Paul Bakaus wrote: > >> Hi Jonas, >> >> Thanks for this I feel this is heading somewhere, finally! I still need >> to work on submitting my full feedback, but I'd like to mention this: >>Why >> did nobody

Why not be multiEntry and array keyPath togather?

createIndexAPI specification state that "If keyPath is and Array and the multiEntry property in the optionalParameters is true, then a DOMException of type No

Re: [screen-orient] why not provide at CSSOM API to CSS Device Adaptation instead?

Hi there, On Wed, Apr 24, 2013 at 2:35 PM, Tobie Langel wrote: > On Wednesday, April 24, 2013 at 1:00 PM, Kenneth Rohde Christiansen wrote: >> Hi there, >> >> CSS Device Adaptation should hopefully be enabled on all browsers (desktop >> and mobile) unlike the viewport meta tag, which cannot be e

URL comparison

Background reading: http://dev.w3.org/csswg/selectors/#local-pseudo and http://url.spec.whatwg.org/ :local-link() seems like a special case API for doing URL comparison within the context of selectors. It seems like a great feature, but I'd like it if we could agree on common comparison rules so t

Re: [IME] Preparing some feedback

Hi Travis, Thanks for the detailed spec and comments! I'll read it through and will post comments on them. On Thu, Apr 25, 2013 at 3:41 AM, Travis Leithead < travis.leith...@microsoft.com> wrote: > Kenji, et al.: > > ** ** > > We appreciate the work you’ve put into this IME API spec so far