Re: [w3ctag/design-reviews] Early design review of the **updated** Multi-Screen Window Placement API (#602)

Thanks for these inquiries!

@torgo: The API was adopted as a Second Screen Working Group deliverable, see the [latest charter](https://www.w3.org/2022/03/charter-secondscreen-wg.html#:~:text=the%20Working%20Group.-,Multi%2DScreen%20Window%20Placement,-An%20API%20that) and [CfC to publish a FPWD](https://lists.w3.org/Archives/Public/public-secondscreen/2022Jun/0010.html). We are getting [valuable feedback from Mozilla](https://github.com/mozilla/standards-positions/issues/542), which just [continued at a recent SS WG vF2F](https://www.w3.org/2022/06/07-webscreens-minutes.html#:~:text=Public%20Working%20Draft-,Mozilla%27s%20feedback,-Mozilla%20position%3A%20Multi), but have no explicit positive signals from another implementer.

@atanassov: The [proposal](https://github.com/w3c/window-placement/blob/main/EXPLAINER_initiating_multi_screen_experiences.md#proposal) includes mitigations to limit the potential for accidental misuse or abuse. The spec was recently [updated](https://github.com/w3c/window-placement/pull/100) per [Mozilla's enhancement feedback](https://github.com/mozilla/standards-positions/issues/636), to clarify [Security Considerations](https://w3c.github.io/window-placement/#security) around deceptive cross-screen placement. The API's [questionnaire](https://github.com/w3c/window-placement/blob/main/security_and_privacy.md) generally covers this minor enhancement, but the Spec and Explainer more directly address the pertinent considerations of this change.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/602#issuecomment-1154265904
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/602/1154265904@github.com>