(CC-ing public-webapps and www-style since I think this API needs more
eyes on it)
Hi,
Web Animations currently has the following API[1]:
interface AnimationEffectReadOnly {
readonly attribute AnimationEffectTimingReadOnly timing;
readonly attribute ComputedTimingProperties comp
> On Sep 29, 2015, at 8:19 AM, Alan Stearns wrote:
>
> On 9/28/15, 4:49 PM, "rn...@apple.com on behalf of Ryosuke Niwa"
> wrote:
>
> Chaals, Art,
>
> Do you have a time preference for this? We’ve got one vote for Tuesday
> afternoon, but I think Monday afternoon could work as well.
>
> I s
On Wed, Sep 30, 2015 at 11:07 AM, Kyle Huey wrote:
> On Wed, Sep 30, 2015 at 10:50 AM, Tab Atkins Jr. wrote:
>> On Tue, Sep 29, 2015 at 10:51 AM, Domenic Denicola wrote:
>>> I guess part of the question is, does this add enough value, or will
>>> authors still prefer wrapper libraries, which ca
On Wed, Sep 30, 2015 at 10:50 AM, Tab Atkins Jr. wrote:
> On Tue, Sep 29, 2015 at 10:51 AM, Domenic Denicola wrote:
>> I guess part of the question is, does this add enough value, or will authors
>> still prefer wrapper libraries, which can afford to throw away backward
>> compatibility in orde
On Tue, Sep 29, 2015 at 10:51 AM, Domenic Denicola wrote:
> I guess part of the question is, does this add enough value, or will authors
> still prefer wrapper libraries, which can afford to throw away backward
> compatibility in order to avoid these ergonomic problems? From that
> perspective,
On Wed, Sep 30, 2015 at 3:13 AM, David Rajchenbach-Teller <
dtel...@mozilla.com> wrote:
> Joshua, I am trying to understand how your proposal relates to
> microtasks. Does the extension of lifetime mean that a transaction is
> alive 1/ until the end of the event (including pending microtasks) or 2
IDB already aborts the transaction if errors are thrown in callbacks.
Additionally, in the promise proposal, if the promise passed to .waitUntil
rejects, the transaction aborts. Does this address your concerns?
On Wed, 30 Sep 2015, 08:26 Conrad Irwin wrote:
> One of the things I like about the W
One of the things I like about the WebSQL API is that the transaction
aborts if any queries fail or if any callbacks throw errors. This way the
whole transaction can be handled as a promise easily, which provides nice
abstraction to the calling code.
It comes at the expense of each individual oper
On 30/09/15 08:12, Jake Archibald wrote:
> I agree with Jonas, I'd like to see IDBRequest and IDBTransaction be
> thenables. This could be done by having a hidden promise, and having
> .then/.catch proxy to the same methods on the hidden promise.
>
> We just have to get over the throw/reject thing
Very good initiative.
Joshua, I am trying to understand how your proposal relates to
microtasks. Does the extension of lifetime mean that a transaction is
alive 1/ until the end of the event (including pending microtasks) or 2/
that it can be kept alive across several events?
Intuitively, I belie
10 matches
Mail list logo
