| 07:55 | <annevk> | wanderview: https://github.com/whatwg/fetch/pull/146 |
| 09:50 | <philipj> | Ms2ger: How is one supposed to use promise_rejects in testharness.js? You added it but I can't see it used anywhere. |
| 09:50 | <philipj> | annevk: yt? |
| 09:52 | <Ms2ger> | philipj, https://github.com/w3c/web-platform-tests/pull/1490/files |
| 09:52 | <Ms2ger> | (In case you ever wanted to write tests for webcrypto: don't bother) |
| 09:52 | <annevk> | philipj: more or less |
| 09:56 | <philipj> | Ms2ger: so it depends on promise_rejects being called before the then() and catch() inside promise_test are registered. I thought maybe it was intended to be used together with a bare async_test. |
| 09:56 | <Ms2ger> | You ask me like you think I have code from a year ago paged in :) |
| 09:57 | <gsnedders> | Well, you should. Obviously. |
| 09:57 | <philipj> | Ms2ger: I expect nothing less from you :) |
| 09:57 | <philipj> | annevk: Do you expect that Gecko will implement webkitMatchesSelector()? |
| 09:58 | <philipj> | annevk: And do you have the full story about how it went from matchesSelector() to just matches()? |
| 09:58 | <annevk> | philipj: I expect we will |
| 09:58 | <Ms2ger> | I expect we have |
| 09:59 | <Ms2ger> | https://bugzilla.mozilla.org/show_bug.cgi?id=1216193 shipping in 44 |
| 09:59 | <philipj> | Ms2ger: was this the first webkit-prefixed method to be added to Gecko? |
| 09:59 | <annevk> | philipj: not the full story, I ended up taking it from http://dev.w3.org/2006/webapi/selectors-api2/ which I assumed had agreement |
| 09:59 | <annevk> | philipj: I believe it was renamed because the other name was too long |
| 09:59 | <philipj> | annevk: I'm using this as a case study in the talk Rick Byers and I are giving at BlinkOn |
| 10:00 | <annevk> | philipj: it has been matches() since June 2012 it seems in the draft |
| 10:00 | <annevk> | philipj: well, per the published draft, not sure when it changed in the editor's copy |
| 10:01 | <philipj> | annevk: jQuery noticed the change in 2013-03: http://bugs.jquery.com/ticket/13629 |
| 10:02 | <philipj> | Ms2ger: grep says the answer is yes. Would you happen to know what the first webkit-prefixed CSS properties in Gecko were? |
| 10:05 | <philipj> | Ms2ger: And if you have any good stories about site compat that contains lessons for Blink developers, I'm making a collection :) |
| 10:07 | <Ms2ger> | https://bugzilla.mozilla.org/show_bug.cgi?id=837211 is relevant |
| 10:08 | <Ms2ger> | Also https://bugzilla.mozilla.org/show_bug.cgi?id=1132745 |
| 10:08 | <Ms2ger> | https://bugzilla.mozilla.org/show_bug.cgi?id=1160281 |
| 10:09 | <annevk> | philipj: ah right, only the prefix variant was implemented |
| 10:09 | <annevk> | philipj: that's probably why editors assumed the change was safe while in fact it was already too late |
| 10:14 | <philipj> | annevk: Right, it was prefixed only for a very long time, and I guess this was before anyone had understood what fallback code looks like, or they thought that libraries would update and propagate the change. |
| 10:15 | <philipj> | Ms2ger: thanks! |
| 10:15 | <Ms2ger> | > they thought that libraries would update and propagate the change. |
| 10:15 | <Ms2ger> | lol |
| 10:15 | <philipj> | Ms2ger: right, but there must have been a time where that seemed plausible |
| 10:16 | <gsnedders> | and they thought that people would update the libraries |
| 10:17 | <philipj> | gotta go |
| 10:26 | jgraham | doesn't remember a time when people believed that libraries would update |
| 10:26 | <jgraham> | Well maybe in 2005 or something |
| 10:26 | <jgraham> | "people" being clueful people ofc |
| 10:26 | <jgraham> | Some peopel still think that |
| 10:32 | <annevk> | philipj: I think it's very similar to the fullscreen situation |
| 10:32 | <annevk> | philipj: which I suppose is largely my fault for insisting fullscreen is a single word |
| 12:07 | <annevk> | mkwst: https://github.com/whatwg/fetch/issues/39#issuecomment-141043738 |
| 12:08 | <annevk> | Would https://github.com/whatwg/fetch/issues/19 be fitting for the HTML Standard? |
| 12:08 | annevk | isn't quite sure where to move it |
| 12:49 | <philipj> | annevk: yep, I guess that one's on you :) |
| 12:50 | <annevk> | fullScreen is fairly hideous though |
| 13:58 | <Ms2ger> | annevk, so is webkitFullScreen ;) |
| 14:03 | <philipj> | annevk: navigator.onLine is my favorite capitalization |
| 14:06 | <gsnedders> | philipj: wat. |
| 14:07 | <philipj> | gsnedders: awesome, right? |
| 14:08 | <gsnedders> | philipj: if by "awesome" you mean "makes me want to rip my eyes out", yes. |
| 14:08 | <philipj> | yes, isn't that what the dictionary says? |
| 14:09 | <gsnedders> | uhhh |
| 15:27 | <zcorpan> | https://zcorpan.github.io/live-webvtt-viewer/ |
| 15:28 | <zcorpan> | i don't know why it doesn't work in firefox |
| 15:34 | <gsnedders> | Hixie: the csswg-test contains tests originally from hixie.ch that have been imported, but with some images. I presume you're happy licensing-wise to include them? |
| 15:34 | <gsnedders> | Hixie: with some images still referencing hixie.ch, I mean |
| 15:56 | <rits> | annevk: Hello, submitted the proposal, do you want to suggest any particular ideas for it, the deadline is today for the proposal submissions |
| 16:08 | <wanderview> | JakeA: ping |
| 16:08 | <wanderview> | sorry, unping |
| 16:11 | <JakeA> | wanderview: no worries! Let me know if there's anything else you don't need me for :D |
| 16:11 | <wanderview> | I found the text in the spec |
| 16:11 | <wanderview> | JakeA: was wondering if the waitUntil() timeout killing a long running worker was spec'd to fail install... and it is |
| 16:12 | <JakeA> | ahhhh, yeah, that sounds like the right thing to do |
| 16:12 | <wanderview> | " If task is discarded or the script has been aborted by the termination of installingWorker, set installFailed to true." |
| 16:36 | <hsivonen> | https://streams.spec.whatwg.org/#transform-stream talks about a text decoder being a kind of a transform stream |
| 16:36 | <hsivonen> | but |
| 16:36 | <hsivonen> | streames otherwise seem to deal with bytes while text in JS is UTF-16 |
| 16:37 | <hsivonen> | are there actually byte streams and UTF-16 streams? |
| 16:37 | <wanderview> | hsivonen: ReadableStream() can pass chunks of any type.... its up to the producer of the stream to say what the type is |
| 16:37 | <hsivonen> | searching the spec for the obvious words doesn't result in search matches explaining this |
| 16:38 | <hsivonen> | wanderview: ok. https://streams.spec.whatwg.org/#chunk could use way more explanatory text |
| 16:38 | <wanderview> | hsivonen: if you don't mind, best way to get it fixed is to file an issue: https://github.com/whatwg/streams/issues/new |
| 16:39 | <hsivonen> | wanderview: ok |
| 16:40 | <hsivonen> | is there a place where text decoding in Streams is being specced for the case where the stream with Uint8Array chunks doesn't guarantee chunks to contain complete byte sequences from the point of view of an encoding? |
| 16:41 | <hsivonen> | i.e. does the text decoder transform exist spec-wise yet? |
| 16:41 | <wanderview> | hsivonen: I'm not sure if work has begin to integrate streams into other APIs yet, besides fetch() |
| 16:42 | <wanderview> | hsivonen: I guess Domenic would know, though |
| 16:42 | <hsivonen> | wanderview: OK. thanks. |
| 16:43 | <wanderview> | hsivonen: there is some question if things should take streams or Response objects... since Response objects also have headers |
| 16:47 | <wanderview> | hsivonen: it seems you could also file a bug against the encoding spec to add streams support: https://github.com/whatwg/encoding/issues |
| 16:47 | <hsivonen> | wanderview: OK |
| 16:54 | <hsivonen> | it looks like TextDecoder spec already has streaming support but eof handling in the streaming case doesn't work |
| 16:54 | <hsivonen> | as in |
| 16:54 | <hsivonen> | doesn't work in our impl |
| 16:54 | <hsivonen> | and I don't see the spec covering the case properly |
| 16:56 | <wanderview> | JakeA: what about if the browser timeouts out activateEvent.waitUntil()... is the SW still active? the spec suggests it should be... see steps 16 and 17 here: https://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html#activation-algorithm |
| 17:05 | wanderview | files an issue |
| 17:06 | <annevk> | rits: I was planning to review the proposals sometime this week, several have applied thus far |
| 17:06 | <annevk> | rits: no thoughts at the moment |
| 17:07 | <annevk> | wanderview: did you see my request for review? |
| 17:07 | <annevk> | wanderview: https://github.com/whatwg/fetch/pull/146 |
| 17:07 | <wanderview> | annevk: no, I did not |
| 17:07 | <wanderview> | I'll look today |
| 17:08 | <rits> | annevk: ok sure :) |
| 17:10 | <annevk> | wanderview: thank you |
| 17:11 | <annevk> | rits: still recovering a bit from the jet lag too, got back last night |
| 17:12 | <wanderview> | JakeA: found the answer to my last question... filed a spec issue for a note, though: https://github.com/slightlyoff/ServiceWorker/issues/776 |
| 17:13 | <rits> | annevk: oh, no problem, you took out the time to review my application in your busy schedule that was enough for me, thanks a lot for that :) |
| 17:19 | <annevk> | wanderview: btw, opaque stream is basically a stream for all intents and purposes but only privileged code (read: the user agent) gets to see the bytes |
| 17:21 | <annevk> | wanderview: and thank you in advance for the review |
| 17:24 | <wanderview> | annevk: this seems to create a whole new vector of opaque tainting to be implemented... |
| 17:25 | <wanderview> | annevk: pass an opaque stream to a DOM implemented decoder, and the decoder has to produce an opaque stream, right? |
| 17:25 | <wanderview> | etc, etc |
| 17:30 | <yhirano_> | wanderview: what do you mean by "a DOM implemented decoder"? |
| 17:31 | <wanderview> | yhirano_: like if https://encoding.spec.whatwg.org/ grew support for streams... it would in theory be a transform |
| 17:31 | <wanderview> | yhirano_: yet, if it took an opaque stream it would now have to be smart enough to pass on the opaqueness, etc |
| 17:32 | <wanderview> | yhirano_: maybe we need this, but it seems to add some non-trivial complexity |
| 17:33 | <wanderview> | yhirano_: for example, var r = new Response(url, { body: anOpaqueBody }) gives a non-opaque Response with an opaque body... that has to be propagated through Cache, etc... |
| 17:33 | <yhirano_> | wanderview: Body.text() and so on don't recognize opaque streams. I thought it would be similar for other decoders |
| 17:35 | <wanderview> | yhirano_: well I guess thats the question... what recognizes these things and what doesn't... its hard to tell from the current spec issue |
| 17:38 | <yhirano_> | wanderview: agreed. |
| 19:49 | <Krinkle> | I'm trying to figure out what the intended guarantees are with regards to requestIdleCallback. Specifically around what happens if the request context gets closed before the queue is exhausted. Maybe when the second parameter is passed, it is expected to run in case of page unload? I'm implementing a very basic fallback but want to make sure behaviour is the |
| 19:49 | <Krinkle> | same. |
| 19:49 | <Krinkle> | The semantics rather. |
| 22:10 | <jsbell> | odinho: Just for the sake of process, do you want to give the objectStoreNames test approval via https://critic.hoppipolla.co.uk/r/5899 ? |
| 22:18 | <odinho> | I prefer critic, -- but for some reason didn't use it on the first of your reviews :) |
| 22:19 | <odinho> | jsbell: critic is not required, -- can use the GH review system (though it's quite bad for bigger reviews) :) But I clicked the button in critic now :9 |
| 22:20 | <jsbell> | odinho: Okay, just don't want to face the angry wrath of j-graham :) |
| 22:22 | <odinho> | ^_* |
| 22:36 | <jsbell> | odinho: want to do the merge? (I seem to recall instructions saying "do not hit the merge button in the web ui" but not finding them now...) |
| 22:37 | <jsbell> | Sorry, feeling rusty. :P |
| 22:41 | <odinho> | :P |