arturjanc

I think a footnote could be a good compromise here, and it has the benefit of not requiring substantial changes. If we do this, it may also be nice to...

It's a little hard for me to understand the entire shape of this proposal (I skimmed the [explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/EyeDropper/explainer.md) and this thread, but I feel like I'm still missing some details),...

I vaguely remember us having a discussion about this where the takeaway (or at least _my_ takeaway) was that this case is fairly easy to solve application-wide by using the...

I think it would be a bit silly to _object_ to this proposal; it's a minor ergonomic change which will make TT adoption easier, it seems simple spec- and implementation-wise,...

Everyone on this thread has already seen and contributed to the doc, but for completeness: The question of whether CORP should be treated as legibility or embeddability, and the consequences...

We had a short discussion about this and I wanted to leave a quick note about the security of this API. In general, there seem to be ways of implementing...

`postMessage()` lets you communicate only with a window to which you have a reference (or, possibly in this case, would have had a reference if it wasn't for COOP). The...

I'm probably missing something, but I don't think this would prevent same-origin documents from using the other APIs to communicate, as long as they're within the same storage partition; e.g....

Yeah, no disagreement from me here: this would certainly require figuring out a way to pass data around between BCGs intentionally separated by COOP. I guess my question is whether...

This is definitely a possible approach, but practically it will mean that -- until WebID ships in most browsers -- authors of OAuth flows will have to switch to one...