| 06:17 | <annevk> | zcorpan: ping on https://github.com/whatwg/html/pull/12389 |
| 06:20 | <annevk> | Andreu Botella: when the resource selection algorithm reaches step 4 the internal play steps continue with step 2 as far as I can tell. |
| 06:35 | <Tim van der Lippe> | Does anybody how to reach out to Rniwa? They don't appear to be present in this chat room and I would like to ping them on https://github.com/w3c/selection-api/pull/356 (or at least ask whether we should submit PRs to this spec to fix issues we find in Servo) |
| 06:58 | <annevk> | I've pinged him just now. |
| 07:49 | <Noam Rosenthal> | Not sure where you see that; it only stays at NETWORK_EMPTY if there is no media provider/src/source |
| 09:13 | <Luke Warlow> | Which WebIDL parser / syntax highlighter is it that the HTML spec uses? I notice the changes I made to WebIDL syntax for e.g. Reflect="rel" still doesn't syntax highlight correctly but I did update the two linked parsers |
| 09:19 | <annevk> | Luke Warlow: highlight is https://github.com/whatwg/html/blob/main/var-click-highlighting.js I think |
| 09:19 | <annevk> | sideshowbarker: ^^ |
| 09:20 | <annevk> | Maybe it's not actually, that script is too small for syntax highlighting. |
| 09:21 | <Luke Warlow> | I think that's for the cross linking highlighting rather than syntax |
| 09:22 | <sideshowbarker> | Yeah for highlighting there was some python thing I set up. I guess we're still using that |
| 09:23 | <sideshowbarker> | And I recall that for webidl we were using Peter’s parser. But I could be misremembering |
| 09:24 | <sideshowbarker> | It's been a long time since I touched that stuff |
| 09:27 | <Luke Warlow> | bs-highlighter it seems it's perhaps this python package, which is derived from bikeshed itself |
| 09:31 | <Luke Warlow> | https://github.com/tabatkins/highlighter - okay so it looks like it might just be that this needs its dependencies bumped and then hopefully the rest will fall out of that. |
| 12:34 | <zcorpan> | annevk: What should we do with doc-PiP? |
| 13:02 | <annevk> | zcorpan: I'm not sure. It doesn't really feel like it meets the bar given there's no good cross-platform story. |
| 13:39 | <zcorpan> | annevk: Would webkit's position change if we (or chromium) were to add support on mobile? |
| 17:27 | <Andreu Botella> | Yeah, the only way that networkState could be NETWORK_EMPTY is if there's no media provider/src/source, but calling play() or clicking a play button won't change that |
| 17:29 | <Andreu Botella> | AFAICT, if you ever make any change that gives the media element a provider/src, that will already invoke the resource selection algorithm by itself |
| 17:30 | <annevk> | zcorpan: I'm not sure, as that's obviously not our primary objection here. I'd rather we all invest in making Media Session capable enough for the use cases. |
| 17:30 | <Andreu Botella> | so the only time that the internal play steps will invoke the resource selection algorithm is when it's guaranteed it won't find a media provider/src |
| 17:51 | <Andreu Botella> | ...so, do I understand correctly that the only observable effect of the internal play steps invoking the resource selection algorithm is that immediately after calling play(), networkState != NETWORK_EMPTY? |
| 23:15 | <nektro> | if anyone has a w3c contact that link should likely point to https://storage.spec.whatwg.org/ instead |