| 02:23 | <Domenic> | David Halls: can you file the issue on whatwg/streams instead of here? That is a bit surprising... |
| 11:41 | <sideshowbarker> | Looking at https://github.com/mdn/content/issues/21550 … what’s the Response.json() method useful for? |
| 11:42 | <Andreu Botella> | it was added because it was useful for server-side runtimes that had fetch-based HTTP server APIs |
| 11:42 | <Andreu Botella> | and it wasn't a burden on browsers |
| 11:46 | <Domenic> | It's also useful in service workers |
| 11:54 | <sideshowbarker> | OK. Well, it would be nice to have it documented in MDN — minimally at least with a one- or two-sentence description |
| 11:55 | <Andreu Botella> | it creates a response corresponding to the JSON serialization of the passed object |
| 11:57 | <sideshowbarker> | Ideally somebody who’s already familiar with it would write up an MDN patch… |
| 11:57 | <sideshowbarker> | Andreu Botella: speaking of patches, I don’t know if you’ve had a chance to look at https://github.com/w3c/csswg-drafts/pull/7886, but I’m wondering if there’s any reason you’re aware of that we can’t/shouldn’t use symlinks instead of redirects |
| 11:58 | <Andreu Botella> | There's no technical reason why not to use that, but I would prefer redirecting. |
| 11:59 | <Andreu Botella> | Ideally HTTP redirects, of course, but Github Pages doesn't support them |
| 11:59 | <sideshowbarker> | Why would you prefer redirecting? |
| 12:00 | <sideshowbarker> | From a user point of view, it seems like redirecting is subobtimal |
| 12:01 | <sideshowbarker> | and https://drafts.csswg.org/ uses symlinks rather than redirects |
| 12:04 | <Andreu Botella> | From a user point of view, it seems like redirecting is subobtimal |
| 12:05 | <sideshowbarker> | I see |
| 12:05 | <sideshowbarker> | I wonder whether most users would see that as preferable |
| 12:06 | <sideshowbarker> | Also, at MDN we have a policy of linking to the un-leveled shortnames |
| 12:07 | <sideshowbarker> | we never link to the specific levels except in case of features that are on some higher leveled version but not in the current-work version |
| 12:09 | <Andreu Botella> | yeah, I guess that's fine then |
| 13:06 | <Domenic> | OK. Well, it would be nice to have it documented in MDN — minimally at least with a one- or two-sentence description |
| 13:07 | <Domenic> | Related to https://github.com/orgs/mdn/discussions/248 |
| 13:10 | <Domenic> | Being redirected to version-specific URLs is quite unfortunate, and a big downside of w3c.github.io over the old csswg-drafts server. I don't like knowing my links will become obsolete in the future. |
| 17:17 | <Luca Casonato> | Yeah, I wanted to contribute a patch but I didn’t manage to figure out where to put the new file so it doesn’t conflict with Response.prototype.json. I couldn’t figure it out, and gave up eventually |