Re: Screen Enumeration and Window Placement Update

Thanks for the advice, Anssi and Kenneth!

I filed issues for each of these topics (plus more) and commented on the
TAG review requests.
- Reject the getScreens() Promise with permission denial #29
<https://github.com/webscreens/screen-enumeration/issues/29>
- API design for a single multi-screen boolean #30
<http://github.com/webscreens/screen-enumeration/issues/30>
- Reuse existing Screen interface or add something new? #31
<http://github.com/webscreens/screen-enumeration/issues/31>
- Combine Screen Enumeration and Window Placement proposals? #34
<https://github.com/webscreens/screen-enumeration/issues/34>
- Scope of the initial proposal #15
<http://github.com/webscreens/screen-enumeration/issues/15>

Thank in advance for feedback on these issues and other aspects of the
proposals,
Mike

On Wed, Jun 10, 2020 at 1:51 AM Kostiainen, Anssi <
anssi.kostiainen@intel.com> wrote:

> Hi Mike,
>
> Thanks for summarizing the key topics, very helpful.
>
> I discussed with W3C TAG member Kenneth and he pointed out the topics
> listed below would be also appropriate to be discussed in the context of
> the preexisting TAG reviews for these capabilities, in [1] and [2]
> respectively. The TAG review was scheduled for this week's TAG call, but
> got pushed out one week. The process for revising a TAG review request is
> simply to add comments to respective TAG review requests with these
> amendments.
>
> In parallel to the TAG review I encourage the Second Screen participants
> to review these proposals as well.
>
> Mike - to facilitate feedback solicitation, I suggest you open GH issues
> for these topics and link them to the TAG issue so all discussions and
> feedback from TAG and Second Screen groups is cross-linked and accessible.
>
> We look forward to addressing these issues together and getting these new
> capabilities in the hards of web developers.
>
> Thanks,
>
> -Anssi (Second Screen WG/CG chair)
>
> [1] https://github.com/w3ctag/design-reviews/issues/413
> [2] https://github.com/w3ctag/design-reviews/issues/522
>
>
> On 10. Jun 2020, at 1.53, Mike Wasserman <msw@google.com> wrote:
>
> Hey Second Screen folks,
>
> I have been refining Screen Enumeration
> <https://github.com/webscreens/screen-enumeration> and Window Placement
> <https://github.com/webscreens/window-placement> explainers and companion
> docs to better reflect the scope of our initial proposal.
>
> There are some specific topics where I'd appreciate feedback:
>
>    1. How to handle rejected permission
>    <https://github.com/webscreens/screen-enumeration/blob/master/EXPLAINER.md#handling-blocked-permissions>: reject
>    promise & fire exception / fulfill with empty info / fulfill with [
>    window.screen ]
>    2. API shape for limited info requests
>    <https://github.com/webscreens/screen-enumeration/blob/master/EXPLAINER.md#requests-for-limited-information>: eg.
>    getScreens(['multiscreen']) -> { multiscreen: <bool> } to get a single
>    bool, perhaps w/o permission
>    3. Nuances of window.screen compatibility
>    <https://github.com/webscreens/screen-enumeration/blob/master/EXPLAINER.md#compatibility-with-the-existing-windowscreen-object>: new
>    props on window.screen, screen.orientation lock and event handler on other
>    screens
>    4. Limiting Window Placement V1 scope
>    <https://github.com/webscreens/window-placement/blob/master/EXPLAINER.md#current-goals>:
>    current goals have been scaled back; lots moved to additional
>    explorations
>    <https://github.com/webscreens/window-placement/blob/master/additional_explorations.md>
>
> Feel free to share any feedback by filing Github issues, replying here, or
> contacting me directly.
>
> Thanks!
> Mike
>
>
>