| 02:55 | <dd perdana2> | hallo every body |
| 07:14 | <Kaiido> | Hello, all. I just noticed a small typo in a section's id in the DOM specs and am not sure what's the best action (since this is used as link, maybe in many places). The section is https://dom.spec.whatwg.org/#action-versus-occurance I guess fixing it is not worth the trouble of potentially breaking existing links? (The readable text is fine) |
| 07:16 | <sideshowbarker> | Howdy Kaiido: it’s possible to add a new ID while preserving the existing ID |
| 07:17 | <Andreu Botella> | Usually ID's are autogenerated from the heading text, at least in Bikeshed, and if this one isn't, it might be because the typo was fixed in the heading but the ID had to stay the same to avoid breaking links |
| 07:18 | <sideshowbarker> | that particular ID is hardcoded in the source, for some reason |
| 07:18 | <Andreu Botella> | I also see British "initialisation" in the ID with American "initialization" in the dfn text sometimes |
| 07:19 | <sideshowbarker> | I also see British "initialisation" in the ID with American "initialization" in the dfn text sometimes |
| 07:19 | <Kaiido> | Yes I would also have thought https://dom.spec.whatwg.org/#action-versus-occurence would be working but it doesn't. |
| 07:20 | <sideshowbarker> | yeah that’s because of it being hardcoded — that overrides the Bikeshed auto-generation |
| 07:20 | <sideshowbarker> | but the existing id=action-versus-occurance could be moved to a span child of that h3 |
| 07:21 | <sideshowbarker> | …and then the Bikeshed auto-generation of the ID on the h3 will work as expected, and the existing ID will work too |
| 07:21 | <Andreu Botella> | you see that in any WHATWG specs? |
| 07:21 | <sideshowbarker> | …I think |
| 07:21 | <sideshowbarker> | pretty sure I have actually done that before, in some cases |
| 07:22 | <sideshowbarker> | https://html.spec.whatwg.org/multipage/timers-and-user-prompts.html#timer-initialisation-steps |
| 07:24 | <sideshowbarker> | https://ian.hixie.ch/bible/english |
| 07:26 | <sideshowbarker> | but I think Hixie always had the spec as lang=en-US-hixie so that “initialisation” would have always been a bug anyway |
| 11:21 | <Jake Archibald> | When adding spec data to JS objects, I've seen some people use internal slots, whereas others just say "SomeObject has a <dfn for="SomeObject">thing</dfn>". Is there a 'right' way? |
| 11:21 | <Jake Archibald> | I usually just do the latter |
| 12:24 | <Jake Archibald> | Also, if a callback is put in an internal slot, does it impact the this value in the callback when it's called? |
| 12:44 | <Domenic> | I prefer the latter, and am somewhat responsible for introducing the former |
| 12:45 | <Domenic> | Is a callback a Web IDL callback, or an algorithm? Web IDL callbacks need to be called with specific thisArgs via https://webidl.spec.whatwg.org/#invoke-a-callback-function |
| 14:42 | <Jake Archibald> | It's a WebIDL callback. Ok, I'll move the shared element transition spec away from internal slots |
| 14:42 | <Jake Archibald> | ta! |