Re: Futures and transactions

2013-04-09 Thread Joran Greef
The problem with IndexedDB transactions is when you need to start doing any kind of streaming, where there is the potential for the stream write buffer to fill up, e.g. syncing over the network: 1. Get references to objects within a collection within a transaction. 2. Compare these to objects

Re: Screen Orientation API: Feedback

2013-04-09 Thread Jonas Sicking
On Sun, Apr 7, 2013 at 10:44 AM, Lars Knudsen lar...@gmail.com wrote: Hi, Having some background in both webapps and actual browser development (webkit, Nokia N9), I see a few issues with the current proposal (some already mentioned in the mozilla thread about this last year). 1. whatever

Re: Screen Orientation API: Feedback

2013-04-09 Thread Lars Knudsen
On Tue, Apr 9, 2013 at 4:01 PM, Jonas Sicking jo...@sicking.cc wrote: On Sun, Apr 7, 2013 at 10:44 AM, Lars Knudsen lar...@gmail.com wrote: Hi, Having some background in both webapps and actual browser development (webkit, Nokia N9), I see a few issues with the current proposal (some

Re: [webcomponents]: de-duping in HTMLImports

2013-04-09 Thread Dimitri Glazkov
The trick here is to figure out whether de-duping is observable by the author (other than as a performance gain). If it's not, it's a performance optimization by a user agent. If it is, it's a spec feature. :DG On Tue, Apr 9, 2013 at 10:53 AM, Scott Miles sjmi...@google.com wrote: When writing

Re: [webcomponents]: de-duping in HTMLImports

2013-04-09 Thread Scott Miles
Duplicate fetching is not observable, but duplicate parsing and duplicate copies are observable. Preventing duplicate parsing and duplicate copies allows us to use 'imports' without a secondary packaging mechanism. For example, I can load 100 components that each import 'base.html' without issue.

[webcomponents]: de-duping in HTMLImports

2013-04-09 Thread Scott Miles
When writing polyfills for HTMLImports/CustomElements, we included a de-duping mechanism, so that the same document/script/stylesheet is not (1) fetched twice from the network and (2) not parsed twice. But these features are not in specification, and are not trivial as design decisions. WDYT?

Re: [webcomponents]: de-duping in HTMLImports

2013-04-09 Thread Brian Kardell
On Tue, Apr 9, 2013 at 2:42 PM, Scott Miles sjmi...@google.com wrote: Duplicate fetching is not observable, but duplicate parsing and duplicate copies are observable. Preventing duplicate parsing and duplicate copies allows us to use 'imports' without a secondary packaging mechanism. For

Re: [webcomponents]: Re-imagining shadow root as Element

2013-04-09 Thread Dimitri Glazkov
Apologies for not replying earlier. The last few weeks were a bit... uhm... hectic. On Tue, Mar 19, 2013 at 1:57 PM, Jonas Sicking jo...@sicking.cc wrote: On Tue, Mar 19, 2013 at 12:05 AM, Roland Steiner rolandstei...@google.com wrote: .) Being an element, can a shadowroot can itself have a