- From: Raymond Toy <rtoy@google.com>
- Date: Thu, 23 Aug 2018 16:16:56 -0700
- To: Chris Lilley <chris@w3.org>
- Cc: "public-audio@w3.org Group" <public-audio@w3.org>
- Message-ID: <CAE3TgXHhxcfVSmThmBaiT4nxK=bjMdxkC_08B14SvrNSTEEtoA@mail.gmail.com>
Done. The report is available <https://webaudio.github.io/web-audio-api/implementation-report.html>. It's out-of-date, but that's a different issue. On Thu, Aug 23, 2018 at 2:24 PM Raymond Toy <rtoy@google.com> wrote: > > > On Thu, Aug 23, 2018 at 8:52 AM Chris Lilley <chris@w3.org> wrote: > >> >> On 17-Aug-18 01:12, Raymond Toy wrote: >> > Do we need to keep implementation-report.html up-to-date? It was last >> > changed in 2016. >> > >> > If we do need this, I guess it should also be part of gh-pages >> branch.... >> >> >> Ah, that would explain why >> https://webaudio.github.io/web-audio-api/implementation-report.html >> doesn't work (404) >> >> I'll add that to gh-pages. > >> >> > Could we also not just point to https://wpt.fyi/results/webaudio so >> > we don't have to maintain the report manually? >> >> >> Maybe, they kind of do different things. The static report is more of a >> human-readable summary. It can point off to detailed test results if >> those are available somewhere else. >> > Ok. Do we need to update this before CR? > >> >> I'm not understanding why on wpt.fyi the number of tests is different >> for each browser, for example. >> >> I'll have to check.... > > >> -- >> Chris Lilley >> @svgeesus >> Technical Director @ W3C >> W3C Strategy Team, Core Web Design >> W3C Architecture & Technology Team, Core Web & Media >> >> >>
Received on Thursday, 23 August 2018 23:17:30 UTC