W3C home > Mailing lists > Public > public-web-perf@w3.org > August 2015

Re: [RequestAnimationFrame]: thrown exceptions and user experience

From: James Robinson <jamesr@google.com>
Date: Tue, 4 Aug 2015 23:57:53 -0700
Message-ID: <CAD73mdJ15t-_gRfr39T6wvDrQxK7fUbSRgyMc4ZNsF0XuF8_-w@mail.gmail.com>
To: Ms2ger <ms2ger@gmail.com>
Cc: Anne van Kesteren <annevk@annevk.nl>, public-web-perf@w3.org, Boris Zbarsky <bzbarsky@mit.edu>, Cameron McCormack <cam@mcc.id.au>
The processing model for RAF is now defined in the html spec's processing
model. I would recommend looking there and directing whoever sent that
patch to that standard instead. I don't know whether this issue has been
addressed there or not but suspect fixing it over there is more likely to
happen.

- James
On Aug 4, 2015 11:26 AM, "Ms2ger" <ms2ger@gmail.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 06/23/2014 09:45 PM, Boris Zbarsky wrote:
> > On 6/23/14, 3:01 PM, James Robinson wrote:
> >> What is the correct incantation to say "Treat this exception as
> >> uncaught and continue with the algorithm" in the spec?
> >
> > http://www.whatwg.org/specs/web-apps/current-work/#report-the-error
> >
> >
> So can we fix this now? I just got a Servo pull request that squashed
> the exception entirely because this thread has gone ignored for over a
> year.
>
> Thanks
> Ms2ger
>
> -----BEGIN PGP SIGNATURE-----
>
> iQEcBAEBAgAGBQJVwQO/AAoJEOXgvIL+s8n2Ad0H/1TDxEhmcDcG6agwDK3IkXNr
> QVJk5kb0EIXMAxob/M6Dbjot3/CRwYqE1WSnoAtIAplhN5CLNDfN/QnpMlbf7SZ9
> qMHgiEJS+zfAyXLSX5r0qQDFneCEGR6Yokf0wKbxrHkU6iDgF/qKFNYv4YQ+TULX
> 2+EP91yCT7q4tnCx5i8YnOr2rN28z0Q3YE6ao6hUZQEXkSamRNE3yFFdf3R08C/f
> w+voLkDZtdLjwf+DMmfgHbVS0zYKu1bLiHe1/6hzcjmJyAAGriAZ4CFBbp9zfHP+
> /9Uz8TH1TrB8DZbgBIj1S/Df3e3+i8USNvQWT6j3q5IdFpNKBh+m/Ob6MhkCN3g=
> =T7oN
> -----END PGP SIGNATURE-----
>
Received on Wednesday, 5 August 2015 06:58:21 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 August 2015 06:58:22 UTC