Re: [w3ctag/design-reviews] Multi-Screen Window Placement on the Web - Initiating Multi-Screen Experiences (Issue #767)

Hi @torgo, thanks for your consideration and persistence, I apologize for my delayed reply.

1) Regarding Mozilla standards positions ([#636](https://github.com/mozilla/standards-positions/issues/636) and [#542](https://github.com/mozilla/standards-positions/issues/542)): We held promising discussions in webscreens [2022 Q2](https://www.w3.org/2022/06/07-webscreens-minutes.html#:~:text=Public%20Working%20Draft-,Mozilla%27s%20feedback,-Mozilla%20position%3A%20Multi) and [TPAC 2022](https://www.w3.org/2022/09/16-webscreens-minutes.html#t06:~:text=Mozilla%20standard%20position) meetings. I also merged [#100](https://github.com/w3c/window-placement/pull/100/files) and replied with security consideration clarifications and new mitigation ideas. We are still awaiting a response.

2) Regarding WebKit's standards positions: We are awaiting responses on [#117](https://github.com/WebKit/standards-positions/issues/117) and older webkit-dev requests ([original api](https://lists.webkit.org/pipermail/webkit-dev/2021-June/031903.html) and [this enhancement](https://lists.webkit.org/pipermail/webkit-dev/2022-May/032223.html)), and other forms of outreach have not yet been fruitful.

3) There is a [spec issue for feature-detection](https://github.com/w3c/window-placement/issues/9), which deserves exploration and discussion.

Here are some AIs I can take upon myself, WDYT?
- Open a new TAG spec review request (for the entire spec) as part of our [wide review](https://github.com/w3c/window-placement/issues/110) effort.
- Ping and update standards-positions issues and invite discussion before/during [Second Screen WG/CG - 2023 Q1 virtual meeting #7](https://github.com/w3c/secondscreen-wg/issues/7)
- Continue refining the spec’s security considerations section and feature-detection issue

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/767#issuecomment-1452505572

You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/767/1452505572@github.com>