07:56 | <Ms2ger> | I like how https://lists.w3.org/Archives/Public/public-review-announce/2015May/0001.html contains JS |
13:51 | <smaug____> | has there been a proposal to add an option to requestAnimationFrame to call callbacks async after the animation frame |
13:52 | <smaug____> | so, requestionAnimationFrame(function() { /* do something after painting*/}, { runCallback: "afterAnimationFrame"} ) |
13:53 | smaug____ | files a bug |
13:55 | <caitp-> | but wouldn't the api be so much more elegant if requestAnimationFrame returned a promise that let you add post-animation-frame behaviour to /* and the promise-y nightmare-bikeshed-discussionpocalypse begins :p */ |
13:58 | smaug____ | suggesting using Promise for anything... |
13:58 | <smaug____> | the world hasn't ended yet |
13:59 | <smaug____> | anyhow, I certainly don't want to make existing function to start to return Promise |
14:00 | <smaug____> | and requestAnimationFrame already returns the identifier |
14:01 | <caitp-> | hah |
14:02 | <caitp-> | yeah I know, but it sounds like the kind of thing that will probably come up |
14:02 | <caitp-> | for better or for worse |
14:04 | <smaug____> | well, that is kind of separate thing anyhow |
14:05 | <smaug____> | I guess it is possible that there will be requestAnimationFrame which returns a Promise which is resolved right before browser updates the graphics stuff |
14:14 | <smaug____> | Ms2ger: do you recall where you saw someone talking about mozPressure |
15:42 | <Ms2ger> | smaug____, https://twitter.com/jlongster/status/599030823388610560 |
15:44 | <smaug____> | ah, that |
15:45 | <smaug____> | Ms2ger: I think .pressure should work there |
15:45 | <smaug____> | if it doesn't work, we should fix that |
15:45 | <Ms2ger> | Yeah, I didn't know about .pressure |
16:42 | <gsnedders> | Does anyone have good stats for SCTP connectivity? |
18:41 | <TabAtkins> | Hmm, Ms2ger isn't around, for once. |
18:42 | <TabAtkins> | Well anyway, Ms2ger, I reported the public-review-announce bug to plh (it's his tool that sends those mails) and he fixed it apparently. |
20:12 | <wanderview> | Domenic: posted my benchmarking results: https://github.com/whatwg/streams/issues/320#issuecomment-102513812 |
20:16 | <wanderview> | trevnorris: ^^^ |
20:19 | <trevnorris> | wanderview: thanks. mind if I add a basic callback style benchmark that does the same thing for comparison? |
20:20 | <trevnorris> | also, what does MBP stand for? |
20:20 | <wanderview> | trevnorris: your looking at the wrong tab... the new benchmark is on the second tab |
20:20 | <wanderview> | MBP is macbook pro |
20:20 | <trevnorris> | heh. thanks. :) |
20:20 | <wanderview> | I did not use my mac there because chrome fetch body stream seems to have trouble on mac for some reason |
20:21 | <wanderview> | trevnorris: happy to accept pull requests.... I put the test repo in the tab at the bottom |
20:21 | <wanderview> | note that trying to do a callback itnerface in user space is hard without hitting the setTimeout() throttling... I guess you can use postMessage() in some browsers, though |
20:22 | <trevnorris> | awesome. thanks. |
20:28 | <trevnorris> | wanderview: do I run those by starting the server and then just viewing index.html? |
20:28 | <wanderview> | trevnorris: yes... and then you should start getting results about 10 seconds later... although sometimes the test stalls out |
20:29 | <wanderview> | its not the most stable test |
20:29 | <wanderview> | trevnorris: and you have to use chrome canary or dev edition to get fetch body stream |
20:35 | <trevnorris> | wanderview: okay. so to clarify, none of the tests run w/o canary? |
20:36 | <wanderview> | trevnorris: the second tab in the google doc that are the result of this repo require google canary or dev channel: https://github.com/wanderview/streams-time-echo |
20:36 | <wanderview> | because it uses Response.body.getReader() |
20:37 | <trevnorris> | okay. I just keep getting a 503 when I point it to localhost:5000/ |
20:38 | <trevnorris> | "Cannot read property 'getReader' of undefined " |
20:40 | <trevnorris> | eh? "Chrome Canary is currently not available on the linux platform." well that bites. |
20:41 | <paul_irish> | yah.. :/ https://download-chromium.appspot.com/ will get you a build that's ~an hour old, though it won't auto-update. |
20:44 | <trevnorris> | paul_irish: just tried. segfaults on startup. |
20:44 | <trevnorris> | "[18985:18985:0515/144128:FATAL:browser_main_loop.cc(178)] Running without the SUID sandbox!" |
20:45 | <wanderview> | trevnorris: is there a beta or dev channel build for linux? |
20:45 | <wanderview> | those might work |
20:50 | <trevnorris> | trying them now |
20:59 | <trevnorris> | wanderview: good idea. running the dev release now. though still getting a 503 from the server. |
20:59 | <wanderview> | trevnorris: the server only lets one test run at a time... if it tried to start before and you errored out you probably need to restart the server |
20:59 | <trevnorris> | ah. okay |
21:00 | <wanderview> | its not very robust |
21:00 | <trevnorris> | awesome. seems to be working. you said about 10 seconds? |
21:02 | <trevnorris> | must have ran the tests. cpu spun up and everything. though it never gets past "Starting..." |
21:02 | <wanderview> | trevnorris: it may have stalled out... I've just been restarting the server |
21:03 | <wanderview> | and retrying when that happens |
21:03 | <wanderview> | it sucks |
21:03 | <trevnorris> | heh. okay. |
21:03 | <wanderview> | but this is a throw-away thing so I didn't spend a long time tracking it down |
21:04 | <trevnorris> | sure. makes total sense. |