| 00:33 | <Hamish Willee> | @hamishwillee:matrix.org Just replied to your responsive image client hints questions on GH (thanks for the issues!). Your three-bullet summary of the changes looks accurate. I'll be around here going forward, if you have questions about the spec. "If the value is zero, it indicates that the image will not be displayed." Is this what you would send in the hint for a request to retrieve an image for download (say)? I'm just trying to work out real cases where you'd hint this. |
| 00:35 | <Hamish Willee> | And at some point "we" should create an update to this wonderful article: https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints#device_hints |
| 00:44 | <Eric Portis (he/him)> | I think I was thinking of non-visual UAs (like screen readers) when I wrote that—which might not make sense because IDK if they even send image requests? Logging off for the day but let me see if I can dig up my thinking... downloads are an interesting case that we should think more about, too. |
| 11:33 | <annevk> | I just realized that WebRTC is full of XMLHttpRequest-like naming, e.g., RTCDtlsTransport. It also has RTCDTMFSender and that's what https://w3ctag.github.io/design-principles/#casing-rules lists, but that seems to be an exception. |
| 11:47 | <foolip> | annevk: you may be amused to know that EdgeHTML had RTCDtmfSender… |
| 11:51 | <annevk> | foolip: so I'm looking into WebRTC a bit more and how can it be that so many things are not defined at all and different between browsers? |
| 11:51 | <annevk> | foolip: basic things like the RTCPeerConnection constructor have many subtle differences |
| 11:52 | <foolip> | Tell me about it, I’ve filed many bugs, many of which were fixed |
| 11:53 | <annevk> | foolip: not sure if you meant that literally, but e.g., should { iceServers: [{urls:[]}] } throw? |
| 11:53 | <foolip> | Why is it like this? I dunno, it’s a very large API surface. Also it doesn’t help that there are relatively few users of WebRTC, so it hasn’t been worn into conformance by the broad masses like happens for DOM and such |
| 11:54 | <annevk> | foolip: where is it defined how the URLs are parsed/processed? |
| 11:54 | <annevk> | Chrome throws for stun:stun1.example.net/, Firefox does not |
| 11:54 | <foolip> | annevk: many were fixed, yes. It used to be that the constructor without arguments would throw! |
| 11:55 | <annevk> | I don't necessarily have a problem with that, as long as it's clear :-) |
| 12:06 | <annevk> | foolip: I filed https://github.com/w3c/webrtc-pc/issues/2660 |
| 12:27 | <foolip> | I don't necessarily have a problem with that, as long as it's clear :-) |
| 12:40 | <foolip> | annevk: Is there any particular reason that you're poking at WebRTC? |
| 12:42 | <annevk> | foolip: https://github.com/w3c/webrtc-pc/issues/2613 |
| 12:44 | <foolip> | annevk: I see, makes sense that you're noticing the things about URLs then. |
| 20:59 | <Domenic> | annevk: smaug: I'm eager to get https://github.com/whatwg/html/pull/6714 merged so we can build on top of it (including for the spec update for https://github.com/whatwg/html/issues/2018 ), so here's another ping :). I wasn't clear if you wanted to wait for smaug's signoff or not. |
| 22:06 | <smaug> | done |
| 22:06 | <smaug> | one day I'll figure out some good way to do spec reviews |
| 22:18 | <Domenic> | Thank you! <3 |