| 02:29 | <sideshowbarker> | Even after doing that thing with the threads button, you can still end up with Element showing that you have unread messages. My element’s been behaving that way for a long time. The only thing which does actually work in that case is to do what Jeffrey said and just use the 'mark as read' button. This is apparently a known issue — see https://github.com/element-hq/element-web/issues/24392 (raised nearly a year ago…). And unfortunately, there’s no option to completely disable threads in Element — see https://github.com/element-hq/element-meta/issues/1090. Per comments in that issue, the Element product team has intentionally chosen not to provide any such disable-threads option — despite the stuck-notifications bug. And given their track record on fixing bugs, it’s very unlikely they’re going to get the stuck-notifications bug fixed any time soon. |
| 02:54 | <sideshowbarker> | PSA: W3C is organizing a remote-only “Breakouts Day” to be held on March 12th. This is an additional day of breakout sessions like the day that’s held during the W3C TPAC each year face-to-face — except this additional one is remote-only. You can propose a breakout session by going to https://github.com/w3c/breakouts-day-2024/issues/new/choose to create a session proposal — though per https://github.com/w3c/breakouts-day-2024/#who-can-propose-a-session you need to be a participant in a W3C group to do that. But that includes W3C Community Groups — and you can directly join on your own any W3C Community Group you want to by going to https://www.w3.org/community/ If you want to get some idea of what kind of topics are in scope, at https://www.w3.org/2023/09/TPAC/breakouts.html#grid you can browse through a hyperlinked table of the titles of the breakout sessions that were held at TPAC 2023 in Sevilla. |
| 09:48 | <Noam Rosenthal> | Anyone has input about the pageconceal event concrete proposal? zcorpan smaug ?I made some progress on the specifics, see https://github.com/whatwg/html/issues/9702#issuecomment-1895379770 |
| 09:51 | <Noam Rosenthal> | (This is the last blocking issue for cross-document view-transitions!) |
| 10:03 | <zcorpan> | Noam Rosenthal: left a comment. Thanks for working on this! |
| 10:05 | <zcorpan> | We should just have a bot that kicks anyone who replies in thread |
| 21:36 | <bakkot> | annevk or whoever: do you know why Fetch provides .arrayBuffer instead of .uint8Array? various other places generally prefer vending Uint8Array, and I found https://github.com/whatwg/fetch/issues/1724#issuecomment-1814626681 which says that "We decided that we'd use Uint8Array generally for byte buffer representation." |
| 21:37 | <bakkot> | maybe it's just that the arrayBuffer method predates the more general tendency to prefer Uint8Array? |
| 22:17 | <Alan Stearns> | Arthur Hemery (and Camille Lamy): what do you think about proposing a “Breakouts Day” session on your proposal for https://github.com/whatwg/html/issues/6364? It might be a way to get some more webkit/gecko input and make some progress. See sideshowbarker’s post above about the breakouts day. |