| 02:07 | <Dominic Farolino> | zcorpan: I see. Hmm, I think I dislike the idea of no line breaks. IMO it makes the source way harder to read and edit :/ I haven't looked at the output of your PR yet since I'd have to check it out locally first, but that would be my initial opinion. |
| 02:22 | <Domenic> | You just gotta turn on word-wrapping in your editor and it's nice, IMO... |
| 06:44 | <Yogya Chugh > | hi |
| 06:45 | <Yogya Chugh > | while reading the DOM standard, I stumbled upon slots and couldn't understand one thing |
| 06:45 | <Yogya Chugh > | what is oldValue here: https://dom.spec.whatwg.org/#slot-name ( just below this link u will find attribute change steps ) |
| 06:52 | <Domenic> | Does following the link to https://dom.spec.whatwg.org/#concept-element-attributes-change-ext clarify it for you? |
| 06:53 | <Domenic> | If not, you might need to follow the call sites backward, by clicking on the bolded definition of "attribute change steps" and looking at where it's called from. (And then where its callers are called from...) |
| 07:42 | <zcorpan> | Dominic Farolino: Most editors have a soft wrapping feature, but don't have an easy way to search for text across lines. But I understand that folks have different preferences. I think a benefit of no wrapping is that contributors don't need to run a formatting script as part of development. |
| 08:37 | <annevk> | keithamus zcorpan: is there a reason https://github.com/whatwg/html/pull/11086 hasn't been merged yet? Not in a rush, just curious why it's still sitting there. Is it the dialog dispute? |
| 08:38 | <keithamus> | I can't merge. I thought the dialog dispute was settled. |
| 08:44 | <zcorpan> | annevk: I think I wanted the an+b issue to settle, but I think it has now so we can merge. Maybe we can switch to :heading(6, 7, 8, 9) though, keithamus ? |
| 08:45 | <keithamus> | Happy to make that change 👍️ |
| 08:47 | <annevk> | Where is the WHATNOT 2025-08-22 issue? It seems mfreed Domenic smaug et al attended and there are notes in the notes document, but not elsewhere? |
| 08:48 | <annevk> | WHATNOT 2025-08-28 also appears to be missing. |
| 08:49 | <keithamus> | IIRC there was a new document started around that time... or maybe I am misremembering |
| 08:50 | <annevk> | I have access to all the documents, but I'm talking about public representation in whatwg/html. |
| 08:50 | <keithamus> | Oh apologies, the issue itself? |
| 08:50 | <annevk> | Yes. |
| 08:51 | <Noam Rosenthal> | I chaired those and I must have missed that step. Is that a matter of copy/pasting them manually to the issue? |
| 08:51 | <keithamus> | Right. Looks like https://github.com/whatwg/html/issues/11648 was the last updated one. |
| 08:51 | <keithamus> | Noam Rosenthal: yes I think you'll want to use that issue as a template, close that one and open new ones (to, I guess, immediately close them) |
| 08:52 | <annevk> | Yes, copy-and-paste with maybe some slight formatting changes to keep it legible. |
| 08:52 | <Noam Rosenthal> | OK let me sort that |
| 08:52 | <Noam Rosenthal> | I think we have issues open for all of them just without the minutes |
| 08:53 | <Noam Rosenthal> | oh we don't. drat. well learning for next time... |
| 09:04 | <Noam Rosenthal> | https://github.com/whatwg/html/issues/11651 |
| 09:39 | <Yogya Chugh > | ok ! Thank you |
| 17:00 | <smaug> | Alice (🇳🇱): how well is reference target tested when it comes to dom mutations? Or perhaps you and dan are working on some more tests? |
| 17:02 | <Alice (🇳🇱)> | That's a bit of a sticky question. It's well tested in Blink: there's a lot that WPTs can't test around accessibility mappings and events (which is what Jamie has been asking about on the FF code reviews) |
| 17:03 | <Alice (🇳🇱)> | there are some WPT test that test that changes are picked up, one moment |
| 17:04 | <Alice (🇳🇱)> | https://github.com/web-platform-tests/wpt/blob/master/shadow-dom/reference-target/tentative/dom-mutation.html |
| 17:05 | <Alice (🇳🇱)> | so yeah, each implementation would need to add their own internal tests for those things |
| 17:06 | <Alice (🇳🇱)> | https://source.chromium.org/chromium/chromium/src/+/main:content/test/data/accessibility/event/aria-treeitem-focus-reference-target.html?q=referenceTarget%20file:test.*accessibility&ss=chromium here's an example Chromium test for the accessibility events |
| 17:09 | <smaug> | setup_nested_reference_target() is quite interesting. And there then adding a new element before inner_host with same id attribute. And then dynamically attaching shadow DOM to that and adding referenceTarget... |
| 17:09 | <smaug> | That kinds of things might reveal the issues I'm worried about |
| 17:21 | <Alice (🇳🇱)> | Yeah, Dan and Alex have done a magnificent job on the WPT tests |
| 17:25 | <smaug> | Right, but I think we need some more 🙂 |
| 17:31 | <Luke Warlow> | Right, but I think we need some more 🙂 |
| 17:32 | <Luke Warlow> | Obviously we can too but the more eyes the better. |
| 17:33 | <smaug> | just by looking at the implementation patches, it is those cases when there are multiple levels of shadow DOMs and the shadow DOMs in between the lowest level shadow DOM and light DOM are changing, in various ways: new elements with same IDs, removing elements, changing IDs, adding new shadow roots dynamically etc |