12:00
<annevk>
keithamus: I created https://github.com/whatwg/html/pull/12562 and am working on test updates. Do you know offhand if HTML AAM needs changes?
12:04
<keithamus>

It won’t, it calls out to computed heading level.

But also I think we want slotted content to correctly compute heading level right? It would be unfortunate to have slotted content not derive its level from the slot and such.

12:22
<annevk>
keithamus: I don't think we want that. That's not what we do for the lang attribute either. The flat tree is mainly for layout and this is not a layout thing.
12:37
<keithamus>

I guess I'd like to discuss this more broadly with folks because I think we really want to use the flat tree. If we don't use the flat tree it'll mean slotted elements can only rely on the host element for offsets which essentially precludes the possibiltiy of making a compositional element which creates a heading heirarchy.

So like

<my-article>
  <h1 slot=title>The title</h1>
  <h1 slot=subtitle>The subtitle</h1> 
</my-article>

Something like this cannot be implemented, where the my-article component is able to slot various headings into the right positions and correctly build a heading heirarchy.

I'm somewhat surprised about lang but I guess there aren't many use cases where a page will switch language, but headings are substantially different to language because every page will have multiple heading levels.

13:22
<annevk>
That's quite far from the original motivation for this feature and I no longer think we want to add slot change invalidation all over the DOM code. In general we've probably been overusing the flat tree.
13:23
<annevk>
I think it would also be surprising for this feature to work fundamentally different from lang and dir.
13:37
<keithamus>
I do agree it's surprising how different it is from lang and dir. I think the use case is important though, I think it aligns with motivations for the feature: composition of heading structures.
14:04
<annevk>
The main use case as I understand it is to be able to insert an existing fragment in a different place. Not arbitrarily re-assign heading levels that don't make sense in their own node tree to begin with.
14:05
<annevk>
Like if you have a blog entry and you want to repurpose that in different templates where the offset ends up being different. I think your example above is quite distinct from that and not something that was discussed or brought up.
16:56
<annevk>
zcorpan: did you see my indeterminate PR? Would be nice to land that if it looks okay
22:32
<annevk>
I'm not sure I understand how Scoped Custom Element Registries ended up in Interop given the state of the tests and spec. It seems Chromium has landed tests that are not backed by the specification and there's still several big PRs in flight as well against DOM, WPT, and HTML, with nobody having really pushed any of those forward.