Keith Cirkel

> My assumption for both of those would be 0 accessibility mappings. I share the assumption, but that me be problematic, and that deviates from `popovertarget` [which Scott has proposed...

For the custom case, maybe a wild idea, but `invoketarget` could call an API on the element which custom elements could then override (bikeshedding very much welcome): ```webidl interface InvokeTargetAriaMappingsReturn...

> if invoketarget can be set without an invoketarget action, then would it even do anything? An `invoketarget` with no `invokeaction` set would be an implicit `invokeaction=auto`, which does things...

It might help to read the draft spec for popover (https://github.com/whatwg/html/pull/9875, the relevant section: https://whatpr.org/html/9875/invokers.html#invoke-target-attribute-activation-behavior), to get a sense of what ambiguities lie (which is to say, I don't think...

> if the default target exists in the DOM, the mappings would be based on that target element, and that's where potential mixing of things seems unclear to me. e.g.,...

I disagree and I think the defaults are an ergonomic win. Less so for video, perhaps, but certainly for dialogs and popovers, where 99% of the time folks are going...

I think we're in agreement on the principle, I can see the point of removing `auto` for `` elements, which would force you to pick an `invokeaction`, but I predict...

It might be good to contextualise what people want. The ability to de-serialize an HTML string into some kind of object model - and back again - is a hugely...

> I think the only reason `new WatchSignal` throws is because `new AbortSignal` throws. Generally you can subclass web platform objects. I've continued to experiment and did manage to successfully...

@jakearchibald also had some insight about 2 years ago, in this thread: https://github.com/whatwg/dom/issues/981#issuecomment-845048934.