| 13:25 | <dminor> | For this particular proposal, I think I'd want to see host integration specified prior to stage 3. Off hand, this feels like ShadowRealms, where the host integration is a potential can of worms and it would be great to see the DOM side of things as soon as possible. |
| 13:27 | <dminor> | Since 2.7 signals ready for testing, and I'd want to see tests for DOM APIs as well, I think the host integration part needs to be specified prior to 2.7. |
| 17:14 | <littledan> | dminor: OK, are you saying that you'd prefer that we have a proposed answer for which AsyncContext.Snapshot is used when calling callbacks from each DOM API, before Stage 2.7? |
| 17:14 | <littledan> | If you'd like to see that ordering, I wonder if we could ask for consensus on the JS side of the design, even if it's without actual stage advancement. |
| 17:15 | <littledan> | The idea is we'd have DOM tests as an entry requirement Stage 3, definitely, either way. Having the final DOM specification before or after 2.7 doesn't change that, I think |
| 17:20 | <dminor> | I'd like to see the DOM API fully specified as soon as possible, so I can get feedback from DOM engineers. |
| 17:22 | <dminor> | In this case, I think it's important to have the DOM side fully specified before entering Stage 2.7, to avoid a situation like with ShadowRealms, where we didn't realize until implementation time the full impact of the proposal on the DOM side. |
| 17:22 | <littledan> | OK, thanks for clarifying! |
| 17:22 | <dminor> | No problem :) |
| 17:22 | <littledan> | I'm happy with this conclusion |