06:28
<annevk>
Domenic: Live URL Viewer is broken
08:38
<annevk>
Kaiido: did you want to review https://github.com/whatwg/html/pull/11601 as well? If not, I'll merge it in a bit.
09:52
<Kaiido>
I won't have much time in the following days to do a full review but from a quick glance it seemed ok to me and it seems your review did spot the potential issues already. So you can merge, I think.
12:37
<annevk>
Luke Warlow: does "validation" mean something for the setter or the getter?
12:38
<Luke Warlow>
For the getter, basically the bit where .control only returns labelable elements
12:38
<Luke Warlow>
Whereas popoverTargetElement (and all other current element reflection properties) return whatever you give them
12:39
<Luke Warlow>
Sorry I'm probably not being very clear, not really sure what to call that behaviour
13:19
<annevk>
Luke Warlow: maybe you could flush forElement out a bit more as an example so it's a bit clearer how it relates to the existing features and what new functionality it would offer.
14:34
<Luke Warlow>
https://github.com/whatwg/html/issues/11577#issuecomment-3292490346 - hopefully this clarifies things a bit. The HTML spec PR for this would be I think a single line change to add the IDL attribute.
14:38
<annevk>
Oh, I already don't like Example 1.
14:40
<annevk>
I also tend to agree with Domenic that it's nicer if it shows the computed value. That's what we do if we can and we clearly can if control can. (Not the computed underlying value, mind. I agree we can't directly expose that.)
14:42
<Luke Warlow>
Does that extend to not exposing an invalid relationship? Whether we expose an implicit valid one I don't really mind. But it would mean a custom getter.
14:58
<annevk>
Luke Warlow: I suppose so. The one scenario that gives me pause is a non-initialized custom element. Perhaps that's a case where you do want to return the element, at least until it's completely clear whether it will do the right thing. But could go either way.
17:03
<mfreed>
Hi all, just a friendly reminder to post any discussion topics for this Thursday's joint CSSWG/WHATWG/OpenUI task force meeting to the meeting agenda issue: https://github.com/whatwg/html/issues/11625