| 03:36 | <sideshowbarker> | For text added with CSS Safari and Chrome find-in-page don’t match on it, but Firefox does. |
| 08:07 | <Domenic> | It's not specified. https://html.spec.whatwg.org/#find-in-page is all we have. |
| 08:08 | <sideshowbarker> | Thanks for confirming |
| 09:03 | <krosylight> | So the opinion from backend: we don't have limit, and that's fine because adding a subscription is pretty cheap actually for backend and there has been no impactful abuse so far (there are other sketchy server behaviors that have more impact) |
| 09:35 | <sideshowbarker> | keithamus: Thanks much for the merge |
| 09:36 | <keithamus> | The journey isn’t over yet 😜. Still gotta integrate and hope it works well enough to not revert |
| 09:36 | <keithamus> | But thanks for pushing it! Would be a welcome improvement! |
| 09:38 | <sideshowbarker> | cheers (and actually it had dropped off my radar a bit — until I got the bot message saying it’d been marked stale (after 60 days) and I only had 7 days to respond before it got closed…) |
| 11:13 | <Luke Warlow> | When the parser spec has text like this, should insert link to something? |
| 11:19 | <Luke Warlow> | Context is I'm trying to track down where the html parser calls the children changed steps of an element (I think it does but the more I look the more I'm not sure) |
| 12:45 | <annevk> |
This doesn't follow. Supported property names are predefined in some fashion. |
| 12:47 | <annevk> | Luke Warlow: I don't think it currently does. And ideally we would link "insert" as well as "create" and "append" (and possibly more in that bit of text) |
| 12:49 | <annevk> | (And this is definitely the right place to chat about this.) |
| 12:51 | <annevk> | Yeah, makes sense for the server. See also the long thread with jrconlin above this one. Still need to figure out if we want to tie the Window entry point to origin though. But maybe that's good enough as a first step. |
| 13:36 | <caitp> | my understanding is, in the case of HTMLCollection, the list of supported names maps to the list of nodes with a matching ID or name in the DOM, or subset of the DOM -- so adding the element to the DOM would alter that set, right? |
| 14:03 | <annevk> | Oh, maybe I didn't look far enough ahead. That does sound correct, yes. |
| 14:09 | <annevk> | Ah, I think you stumbled upon https://github.com/whatwg/webidl/issues/669 |
| 14:11 | <annevk> | Do you want to fix it? You already did all the work justifying how it's tested in WPT today, but I'm also happy to take over I suppose as removing that step is fairly straightforward. 😅 |
| 14:24 | <caitp> | Sure, I can find some time for that |
| 17:57 | <Meghan Denny> | spam https://github.com/whatwg/webidl/issues/1416 |
| 17:57 | <Meghan Denny> | spam https://github.com/whatwg/webidl/issues/1417 |
| 23:10 | <jamescobban> | Hey everyone, I was searching for a website where I can learn some extra topics of JavaScript. Is there any website that has better and deeper content (from basics to advanced) in a sequential order? Your help is greatly appreciated 🙏🏻🙂 |
| 23:35 | <Matthew> | slightly random question: has anyone written down a retrospective of the evolution of web standards recently? |
| 23:35 | <Matthew> | e.g. WHATWG v W3C and how things resolved and evolved |
| 23:35 | <Matthew> | and how the cabal of browser vendors actually get stuff done these days? |
| 23:36 | <Matthew> | i'm trying to get the governance model right for Matrix and trying to debug how others have failed & succeeded. |