WHATWG on 2022-09-24

05:36	<sideshowbarker>	About the `SpeechRecognition` (`webkitSpeechRecognition`) part of the Web Speech API: As far as I can tell, there’s no way to programatically determine what languages the browser recognizes/supports for speech input/recognition, right? In comparison, for the TTS part of the API, I know I can do `window.speechSynthesis.getVoices()` to get an array of the supported voices/languages — but there’s no similar method or property for `SpeechRecognition`. But I wonder if there might be some browser-specific ways to get the supported languages back from Chrome and Safari.
05:39	<sideshowbarker>	I’m also wondering exactly how the speech recognition part of the API works in Chrome and Safari. I’ve gleaned that in Chrome it seems to rely on the browser calling out to some remote Google speech-recognition service. But in the Safari case it seems to be using some built-in macOS speech-recognition platform feature. But… what exactly? And does Edge rely on the same remote Google speech-recognition service that Chrome does?
05:40	<sideshowbarker>	Asking in the context of trying to provide some better documentation in MDN about how `SpeechRecognition` actually works.
08:04	<annevk>	For a while "good first issue" yielded mostly good results, but now it just seems like an endless stream of requests for getting assigned to an issue. Maybe we should go back to a different label (e.g., "beginner") and just outline some instructions for beginners in the README (or through a pointer from there)?
08:05	<annevk>	I suppose we could try to outline some clearer instructions first, but I've the feeling the label contributes due to dedicated GitHub support.
09:23	<sideshowbarker>	Help/comments welcome at https://github.com/mdn/content/issues/20730 The OP asserts “`preventDefault()` doesn't work in Chrome” and objects to MDN marking the `returnValue` property of `Event` as deprecated “despite it being the only working feature across all browsers”.
10:42	<Domenic>	Help/comments welcome at https://github.com/mdn/content/issues/20730 The OP asserts “`preventDefault()` doesn't work in Chrome” and objects to MDN marking the `returnValue` property of `Event` as deprecated “despite it being the only working feature across all browsers”. Seems just... wrong? Ask them to provide proof.
11:03	<sideshowbarker>	Seems just... wrong? Ask them to provide proof. Yeah I guess I should do that, but I'm reluctant to engage with the OP at all, since this seems like a type where there's no possible resolution for their issue that they're going to end up being satisfied with
11:09	<Domenic>	Yeah that's fair
11:09	<Domenic>	I mean there's a slight chance they'll test it, realize they're wrong, and be graceful about it.
12:06	<annevk>	Oh Element (Matrix?) both has a "reply" and a "reply in thread (beta)" feature. Why aren't these one feature.