| 08:50 | <annevk> | Okay, it seems checking tabatkins/bikeshed-data works. And then if you don't see it appear there you ping plinss. |
| 09:14 | <annevk> | Is a child browsing context ever not 1:1 with its navigable? |
| 12:02 | <Domenic> | Is a child browsing context ever not 1:1 with its navigable? |
| 12:03 | <Domenic> | (until everyone has out of process iframe tech and then we can start introducing cool stuff like BCG swaps for iframes?) |
| 12:05 | <annevk> | I don't think that ends up having much meaning as a BCG only cares about top-level BCs. |
| 12:06 | <annevk> | Perhaps this is something we can simplify then whereby we only have top-level BCs. |
| 12:07 | <Domenic> | Hmm. We'd still need WindowProxys for children, but maybe indeed the BC concept is not helpful... unsure. |
| 12:08 | <annevk> | I guess a child browsing context might still be useful as a thing that can be targeted and end up with an opener. Even if we don't replace it. It feels very niche, but maybe I just need to get used to it. |
| 12:09 | <Domenic> | Ugh, children can have openers? That's gross. |
| 12:10 | <annevk> | Name targeting is the original sin, but yes. |
| 12:10 | <Domenic> | I think navigables are the things that are targeted now, but sometimes we decide not to carry over their name when doing a navigation. |
| 12:11 | <annevk> | Hmm, so COOP definitely wants fresh name and such. And name targeting in theory walks through the BCG's TLBCs. |
| 12:11 | <Domenic> | I was really hoping we could collapse "is auxiliary" and "has an opener" but it seems like if children can have an opener that's unlikely... |
| 12:11 | <Domenic> | Maybe moving name to navigable was a mistake then... |
| 12:12 | <annevk> | Yeah, I'm also a little worried about this line:
Because I wouldn't want anyone to be able to cast an even wider net than a browsing context. |
| 12:13 | <annevk> | But if it's for traversal through the tree of documents it seems okay. |
| 12:13 | <Domenic> | It's very rare that a spec (besides HTML itself) wants to have different behavior after BCG swaps. |
| 12:15 | <annevk> | Ah, I guess you're specifically referring to same-origin swaps. And that makes sense. But navigables can span many origins so putting state on them would be rather dangerous. |
| 12:19 | <annevk> | Domenic: "is auxiliary" could maybe still be collapsed but you'd need "has opener" + "is top-level" |
| 12:19 | <Domenic> | Yeah, I guess. Not a big win. |
| 12:20 | <annevk> | But at least the issue isn't wrong. :-) |