On 4/29/15 12:23 AM, Glen Huang wrote:
because of the proxy machinery involved on the JS engine side
Do you mean the cost introduced by passing a C++ object into ecmascript world?
No, it's the cost introduced by needing custom property behavior for
integer-named properties on lists (and in
Dear Web Apps Working Group,
On 16 April 2015, the W3C Web Payments Interest Group [1] published:
Web Payments Use Cases 1.0
http://www.w3.org/TR/web-payments-use-cases/
This document is a prioritized list of Web payments use cases. Guided
by these use cases, the W3C Web Payments Interest
On Wed, Apr 29, 2015 at 4:15 PM, Dimitri Glazkov dglaz...@google.com wrote:
On Mon, Apr 27, 2015 at 8:48 PM, Ryosuke Niwa rn...@apple.com wrote:
One thing that worries me about the `distribute` callback approach (a.k.a.
Anne's approach) is that it bakes distribution algorithm into the platform
On Wed, Apr 29, 2015 at 4:47 PM, Ryosuke Niwa rn...@apple.com wrote:
On Apr 29, 2015, at 4:37 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Wed, Apr 29, 2015 at 4:15 PM, Dimitri Glazkov dglaz...@google.com wrote:
On Mon, Apr 27, 2015 at 8:48 PM, Ryosuke Niwa rn...@apple.com wrote:
One
Will do.
:DG
On Sun, Apr 26, 2015 at 2:08 AM, cha...@yandex-team.ru wrote:
Attached here is a clean version, which will be archived.
Note that there was a lot of sidechat in IRC it is unclear how much of
that everyone in the room was aware of. I hope the minutes are a pretty
accurate
Here's one case of redistribution:
https://github.com/Polymer/core-scaffold/blob/master/core-scaffold.html#L122
Any time you see content inside a custom element it's potentially
redistribution. Here there's on that is (line 122), and one that could be
(line 116), and one that definitely isn't
On Mon, Apr 27, 2015 at 8:48 PM, Ryosuke Niwa rn...@apple.com wrote:
One thing that worries me about the `distribute` callback approach (a.k.a.
Anne's approach) is that it bakes distribution algorithm into the platform
without us having thoroughly studied how subclassing will be done upfront.
On Tue, Apr 28, 2015 at 1:52 PM, Ryosuke Niwa rn...@apple.com wrote:
I've updated the gist to reflect the discussion so far:
https://gist.github.com/rniwa/2f14588926e1a11c65d3
Please leave a comment if I missed anything.
Thank you for doing this. There are a couple of unescaped tags in
On Apr 29, 2015, at 4:37 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Wed, Apr 29, 2015 at 4:15 PM, Dimitri Glazkov dglaz...@google.com wrote:
On Mon, Apr 27, 2015 at 8:48 PM, Ryosuke Niwa rn...@apple.com wrote:
One thing that worries me about the `distribute` callback approach (a.k.a.
On Apr 29, 2015, at 4:16 PM, Dimitri Glazkov dglaz...@google.com wrote:
On Tue, Apr 28, 2015 at 1:52 PM, Ryosuke Niwa rn...@apple.com wrote:
I've updated the gist to reflect the discussion so far:
https://gist.github.com/rniwa/2f14588926e1a11c65d3
Please leave a comment if I missed
On Wed, Apr 29, 2015 at 5:59 PM, Ryosuke Niwa rn...@apple.com wrote:
On Apr 29, 2015, at 4:16 PM, Dimitri Glazkov dglaz...@google.com
wrote:
On Tue, Apr 28, 2015 at 1:52 PM, Ryosuke Niwa rn...@apple.com wrote:
I've updated the gist to reflect the discussion so far:
On Apr 29, 2015, at 5:12 PM, Justin Fagnani justinfagn...@google.com wrote:
Here's one case of redistribution:
https://github.com/Polymer/core-scaffold/blob/master/core-scaffold.html#L122
Any time you see content inside a custom element it's potentially
redistribution. Here there's on
Thanks. As far as my understanding is correct, the conclusions so far are:
- There is no use cases which shadow as function can't support, but
content slot can support.
- there are use cases which shadow as function can support, but
content slot can't support.
- shadow as function is more
13 matches
Mail list logo