Dumb question: why cause these to be module scripts when they're clearly going to be loaded async from the perspective of the main script anyhow? On Sat, Feb 6, 2016 at 7:43 AM, Ian Kilpatrick <ikilpatrick@google.com> wrote: > Hey all, > > I made a bunch of edits during Houdini. > See: https://drafts.css-houdini.org/worklets/ > > Major change is that this will require the modules infrastructure which > was just added to the html whatwg spec. > > lmk if you need anything specifically. > > Thanks, > Ian > > On Thu, Jan 28, 2016 at 9:03 AM, Ian Kilpatrick <ikilpatrick@google.com> > wrote: > >> Hey Paul, >> >> Over the next week I've got some time to spend on it, and aiming it to >> get to a stage where it's good for Houdini. >> >> What are the specific things that you need from it to move forward at the >> moment? >> >> PRs are great if you have the time. >> >> Thanks, >> Ian >> >> On Thu, Jan 28, 2016 at 8:51 AM, Alex Russell <slightlyoff@google.com> >> wrote: >> >>> +shane >>> >>> On Wed, Jan 27, 2016 at 6:46 AM, Paul Adenot <padenot@mozilla.com> >>> wrote: >>> >>>> Ian, >>>> >>>> The Audio-WG (CC-ed) was wondering about the status of the Worklets >>>> specification. There are still a few things that need to be done until we >>>> have enough infrastructure to write the Audio Worklet text on top of it, >>>> and the Web Audio API really need this to go forward. >>>> >>>> Do you have an estimate on when you'll be able to find some time to >>>> work on it? Can we help in any way ? Since this is on the critical path for >>>> us, it might make sense we contribute in a more direct way, by directly >>>> sending PRs. >>>> >>>> Cheers, >>>> Paul. >>>> >>> >>> >> >
Received on Sunday, 7 February 2016 12:01:21 UTC