| 07:26 | <yoav> | zcorpan: Hey! Got an `<audio>` question. if I have `<audio><source src=wav type="audio/wav"><source src=mpeg type="audio/mpeg"><source src=ogg type="audio/ogg"><audio>`, which resources would I expect to download? |
| 07:27 | <yoav> | (Currently in Chromium it seems like the answer is flakily all of them) |
| 07:27 | <annevk> | yoav: I think the first that matches |
| 07:27 | <yoav> | that's what I expect |
| 07:28 | <yoav> | so in this case, the wav one probably |
| 07:28 | <annevk> | I'd have to read the algorithm to be sure though |
| 09:36 | <MikeSmith> | Same-site cookie support in Edge just now moved to “working on it” https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/17140412-support-samesite-cookie-option |
| 09:36 | <MikeSmith> | mkwst: ⬆ |
| 09:37 | <zcorpan_> | yoav: I think mpeg because the mime type for wav is audio/wave iirc. What do browsers do? |
| 09:38 | <yoav> | from what I see Chromium sometimes download all of them, sometimes leaves one or two out :/ |
| 09:38 | <yoav> | https://bugs.chromium.org/p/chromium/issues/detail?id=822757&can=2&start=0&num=100&q=owner%3Ame&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified&groupby=&sort=&hotlist_id= |
| 09:42 | <zcorpan_> | Or maybe audio/wav is supported. Seems there's no registered type in iana... |
| 09:43 | <zcorpan_> | Downloading all of them seems bogus. But maybe that happens if for some reason you can't play anything? |
| 09:44 | <zcorpan_> | Audio is still not fetched speculatively right? |
| 12:11 | <foolip> | annevk: https://chromium-review.googlesource.com/c/chromium/src/+/986136 has working results now, although I suspect you don't need them |
| 12:17 | <annevk> | foolip: still somewhat curious about the locking aspects, but not sure if those are demonstrated there |
| 12:17 | <annevk> | foolip: also interested in the SetSecurityOrigin call |
| 12:17 | <foolip> | annevk: no, don't think that would be caught there |
| 12:18 | <foolip> | annevk: you want to know what tests exercise a particular code path? |
| 12:20 | <annevk> | foolip: or how to construct such a test |
| 13:18 | <annevk> | yhirano: see https://github.com/w3c/web-platform-tests/pull/10817 for why using the document's URL when reloading is likely wrong |
| 13:19 | <annevk> | yhirano: needs to be current entry's URL |
| 14:24 | <wanderview> | JakeA: in case you care, I'm going to change one of your abort WPT tests: https://bugzilla.mozilla.org/show_bug.cgi?id=1458805 |
| 16:43 | <annevk> | Domenic: if you're interested in doing more drive-by reviews, there's quite a few: https://github.com/w3c/web-platform-tests/pulls/annevk |
| 16:47 | <Domenic> | Ah well when you put it that way I feel like I should... |
| 16:48 | <Domenic> | Wow that is a sad number of open tests :( |
| 16:53 | <Domenic> | https://github.com/w3c/web-platform-tests/pull/10548 is a cool test |
| 16:53 | <Domenic> | WTF https://github.com/w3c/web-platform-tests/pull/10679/files the web is so weird |
| 16:54 | <Domenic> | annevk: so I guess I'm having a hard time doing reviews since I'm not sure what's being tested. E.g. there are no "should" statements in the tests. |
| 16:55 | <Domenic> | (for the document.open() tests) |
| 16:55 | <Domenic> | So I can't tell what the tests are meant to be testing, and thus I can't check them to see if they're correct |
| 17:24 | <annevk> | Domenic: ah yeah, I was more looking for test suggestions and such, they're not quite ready yet as we haven't decided what the spec should be in aggregate |
| 17:24 | <Domenic> | Hmm OK |
| 17:26 | <annevk> | Domenic: I mean, I sorta know that Chrome is the way to go; maybe I should double down on that in another pass |
| 19:48 | <smaug____> | any youtube or polymer folks here? I wonder when Youtube might switch to use webcomponents v1 |
| 19:48 | <smaug____> | and drop the chrome only API usage |