- From: Hadley Beeman <notifications@github.com>
- Date: Mon, 15 Jan 2024 09:25:11 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/840/1892553039@github.com>
Thanks for the reply, @Anssiko. Are there alternative proposals for similar functionality that the WG is also considering? Is there is a particular architectural question we can help with, or are you having trouble achieving consensus in a way that we can help with? At this stage, we would recommend that, as a working group, you all work towards consensus and come back to us when you have a single proposal for us to review. Having said all that, we have looked at what you are proposing here and are recording a couple of thoughts as well. We noticed that there isn't specific mention of focus management or accessibility in the explainer. Can you make accessibility considerations explicit in the explainer / spec? Another specific question that came up in our discussion: do you require passing in 4 coordinates of the other screen when targeting a different screen? Passing a screen's label may have better developer ergonomics. Considering the early stage here, we don't think it's appropriate to give a final review on this proposal at this time. You can re-open the issue if you have any specific questions, or feel free to open a new issue with broader architectural concerns. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/840#issuecomment-1892553039 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/840/1892553039@github.com>
Received on Monday, 15 January 2024 17:25:17 UTC