| 03:59 | <MikeSmith> | anybody know if there’s an official logo for Android WebView? |
| 04:00 | <MikeSmith> | I find something at https://cdnjs.loli.net/ajax/libs/browser-logos/41.0.0/android-webview-beta/ that looks familiar, but not certain that WebView is what that logo is really used for |
| 04:28 | <Krinkle> | MikeSmith: for what it's worth, I've mostly seen this logo associated with the pre-Chrome built-in browser, https://github.com/alrra/browser-logos/blob/master/src/archive/README.md#android. That's not technically analogous to the WebView interface as used for embedded in apps though, not sure if you meant actual webview vs default browser. |
| 04:30 | <MikeSmith> | Krinkle: ah OK yeah I guess that’s where I recall seeing it from too |
| 04:30 | <MikeSmith> | and yeah I do want a logo for actual webview, not default browser |
| 04:31 | <Krinkle> | right, a logo app developers would be familiar with, as opposed to end-users. |
| 04:31 | <MikeSmith> | yeah |
| 04:32 | <MikeSmith> | that specific context for me is, the data for MDN’s brower-compatibility tables includes WebView data, and I want to associate a logo with that when I show it |
| 04:32 | <MikeSmith> | similar to caniuse annotations in the HTML spec now |
| 04:33 | <MikeSmith> | but which don’t have WebView data (I guess because CanIUse doesn’t) |
| 04:34 | <Krinkle> | Yeah, they don't track ios embedded webview and android webview currently. |
| 04:34 | <Krinkle> | ua-parser does recognise it though. |
| 04:34 | <Krinkle> | and yeah, behaviour does differ from a little to a lot. |
| 04:35 | <MikeSmith> | right |
| 04:37 | <Krinkle> | I guess for ios webview, the WebKit logo would be most familiar, which since last year's redesign not matches the style of other developer api logos from Apple. |
| 04:47 | <MikeSmith> | Krinkle: well MDN doesn’t track browser-compatiablity data for ios webview, so I don’t need that one (yet) |
| 04:57 | <Krinkle> | in theory it should state that safari has a broken navtiming implementation in webview :) |
| 04:57 | <Krinkle> | (something I've been running into recently) |
| 05:16 | <MikeSmith> | Krinkle: oh |
| 05:16 | <MikeSmith> | weird that it would be different |
| 05:17 | <MikeSmith> | but I guess there’s some rationale for the difference (modulo the unintended brokenness) |
| 08:30 | <hsivonen> | what's the right wpt directory for a reftest that tests the interaction of first-line, first-letter and float? |
| 08:31 | <hsivonen> | ..in relation to bidi |
| 08:38 | hsivonen | wonders how Microsoft feels about the 360 Secure logo/icon |
| 08:43 | <annevk> | hsivonen: I'd use css/selectors |
| 08:44 | <hsivonen> | annevk: even if it really tests float+bidi? |
| 08:45 | <annevk> | hsivonen: yeah, it seems they'd still test those selectors otherwise you'd have left them out |
| 08:45 | <hsivonen> | annevk: ok. thanks |
| 08:46 | <hsivonen> | (deciding the directory for CSS tests is one of the hard problems of wpt) |
| 08:48 | <annevk> | Tree structures for graph problems generally result in this |
| 09:33 | <hsivonen> | aargh. "test case must have a link to a spec" |
| 09:51 | <annevk> | CSS tests have their own weird requirements I guess? |
| 09:51 | <annevk> | I wish they'd just align with the defaults we set elsewhere |
| 10:51 | MikeSmith | recommends hsivonen experiment with putting the empty string for the link URL, or else "#" |
| 11:47 | <annevk> | JakeA: so I looked at Background Fetch's open issues and it seems there's still quite a few, including some I opened a long time ago |
| 11:51 | <JakeA> | annevk: I see https://github.com/WICG/background-fetch/issues/16 and https://github.com/WICG/background-fetch/issues/6. In terms of #16, I can't really see how it'd work. Grouping is needed for things like photo uploads, game downloads, movie downloads etc. Given the delivery of events is a particular service worker it feels like the API should hang off that particular service worker registration. |
| 11:51 | <JakeA> | annevk: As for #6. The spec uses keep-alive, but I'm happy to add test explaining this spec vs `sendBeacon` etc. |
| 11:52 | <annevk> | JakeA: yeah, so to clarify, I'm not sure how relevant they still are, but it seems weird for them to not be resolved |
| 11:52 | <annevk> | JakeA: esp if Google is keen on moving on |
| 11:52 | <JakeA> | annevk: Fair. I'll go through them tomorrow. |
| 12:57 | <JakeA> | annevk: appreciate the review btw |
| 13:00 | <annevk> | JakeA: sorry it's taken so long to do another round |
| 13:00 | <annevk> | JakeA: but it's mostly nits |
| 13:04 | <JakeA> | annevk: starting a spec on my own has taught me a lot tbh. Once this is 'done' it frees me up a bit. Anything I should move on to? I was thinking fetch observer |
| 13:05 | <annevk> | JakeA: that'd be great; refactoring fetch so it returns a struct and doesn't queue tasks would also be cool, but rather involved |
| 13:06 | <JakeA> | annevk: fixing the task queueing might not be too bad, it's just going through everything that currently uses it and queueing tasks when needed. Is the struct thing so there's a concrete thing to abort etc? |
| 13:10 | <annevk> | JakeA: yeah abort, concrete thing to take the response from if you don't care about callbacks and just want to use "wait", and maybe changing priority and such if that ever becomes a thing |
| 13:45 | <annevk> | I always forget whether dictionary or sequence is possible, but I guess it is |
| 14:03 | <smaug____> | has anyone looked at all the specs from GDPR point of view? |
| 14:03 | <smaug____> | or is there some work ongoing perhaps |
| 14:05 | <smaug____> | I guess only very small set of specs need to be looked at |
| 14:08 | <annevk> | smaug____: I'm not aware of any effort |
| 14:09 | <annevk> | smaug____: I guess stuff like push notifications or geolocation might need some GDPR specifics depending on how you implement them? |
| 14:10 | <smaug____> | and maybe Reporting API |
| 14:10 | <annevk> | That's on request from the site, so the site would have to manage that |
| 14:22 | <annevk> | I blocked anshul1719 organiziation-wide |
| 15:54 | <smaug____> | annevk: do you recall some example where some synchronous algorithm needs to dispatch an event, say when an element is disconnected. |
| 15:55 | <smaug____> | I guess it needs to be defined somehow whether to fire event before or after CEReactions |
| 15:56 | <annevk> | If sync it’s always before |
| 15:57 | <annevk> | But we don’t define those atm… |
| 15:57 | <smaug____> | so no examples of this |
| 15:57 | <smaug____> | ok |
| 16:00 | <annevk> | smaug____: mutation events are still tbd |
| 16:00 | <annevk> | smaug____: suspect focus/blur might be affected |
| 16:14 | <smaug____> | right |
| 16:14 | <smaug____> | and this is about pointerevent's pointercapture handling when the target is removed from dom |
| 17:29 | <zcorpan> | Hacking on browsers is fun |
| 17:41 | <Domenic> | annevk: gah the PRs messed up our CI status on master again... will try to fix |
| 18:14 | <Domenic> | Fixed |
| 18:15 | <Domenic> | https://github.com/whatwg/participate.whatwg.org/pull/33 should help for the future |
| 18:46 | <annevk> | Domenic: I can r+ that, but I won't review the whole thing in detail, that okay? |
| 18:46 | <Domenic> | annevk: sure, although the actual code changes are pretty small. Also it's not urgent, unless we expect more of these to happen. |
| 18:48 | <annevk> | Domenic: the actual code looks fine, assuming all the properties are correct 😃 |
| 18:49 | <Domenic> | Yeah, the tests help there, since I pulled that fixture directly from the webhook payload |
| 18:54 | <gsnedders> | FWIW: there's been a bunch of html5lib/html5lib-tests PRs about error expectations recently if anyone who knows hte parser better than me atm can look? |
| 19:16 | <annevk> | Browsers want to align on H/1 request serialization; HTTP editor dismisses entire topic; sigh |
| 19:17 | <annevk> | Either H/1 becomes obsolete or Fetch will define aspects of it the way this is going… |
| 20:35 | <Domenic> | link? |
| 20:36 | <Domenic> | https://github.com/httpwg/http-core/issues/137 |
| 20:39 | <Domenic> | https://github.com/httpwg/http-core/issues/136 is also lovely. What a helpful group of folks. |
| 20:51 | <gsnedders> | is there any evidence of H/1 serialisation as in #137 actually causing issues? |
| 21:20 | <devsnek> | Domenic: how does one test if a stream is cancelled |
| 21:21 | <devsnek> | or anyone i guess |
| 21:49 | <MikeSmith> | Domenic: https://github.com/httpwg/http-core/issues/136#issuecomment-424489058 is gold |
| 21:49 | <MikeSmith> | > Even if five major browsers caught fire and imploded upon receipt of multiple challenges, that would only increase the need for those parsers to be fixed (somehow). We can't control the bits received. The easiest fix is to simply parse the field as specified, since that's what the non-browser UAs have been doing for ages. |
| 21:52 | <MikeSmith> | some serious regime change has been needed there for a long time |
| 21:53 | <MikeSmith> | the web platform needs a CIA |
| 21:53 | <MikeSmith> | with a Seal Team 6 |
| 21:54 | <MikeSmith> | and the IETF needs an Arab Summer |
| 21:57 | <MikeSmith> | “the web should just work the way I claimed it does in my disseration” |
| 21:58 | <MikeSmith> | the Web: “I don’t actually work that way. I never have, actually.” |
| 22:02 | <Domenic> | Dunno about the Seal Team 6 part, but I do like the picture of web pages, in all their dissertation-violating glory, filling the streets of the internet to protest unevenly-implemented de jure specs. |
| 22:10 | <gsnedders> | literal anarchy |
| 22:36 | <Domenic> | devsnek: https://github.com/web-platform-tests/wpt/blob/master/streams/readable-streams/cancel.js#L59 |
| 22:36 | <devsnek> | ic |
| 22:37 | <Domenic> | Although the recordingReadableStream utility should make this easier, trying to find a usage of that |
| 22:37 | <devsnek> | async makes everything harder 😢 |