Multi-Screen Window Placement 2020-11-25 > 2022-12-31

[anssiko]

Name of your specification

Multi-Screen Window Placement

URL of your specification

https://www.w3.org/TR/window-placement/

Do you need a reply by a particular date?

2022-12-31

Please point to the results of your own self-review

w3c/window-management#118

Where and how should the i18n WG raise issues?

https://github.com/w3c/window-placement/issues/

Pointer to any explainer for the spec

https://github.com/w3c/window-placement/blob/main/EXPLAINER.md

Other comments

The following two explainers cover the Multi-Screen Window Placement feature scope in review: incremental improvements to existing screen information and window placement APIs and API enhancements to allow initiation of multi-screen experiences from a single user activation. These explainers should be read in that order.

We believe there are no internationalization considerations for this API at this time. However, we look forward to addressing any i18n issues or documenting any i18n considerations. We have prepared an Internationalization Considerations placeholder section for the latter. Thank you for your review!

[aphillips]

@anssiko Thanks for the review request. Can you please clarify the due date? Do you have a transition planned? Due to holidays and such at this end of the year, we may not have time to complete this review by 31 December. Thanks.

[anssiko]

This specification was published as a First Public Working Draft in June 2022 and we've done a few WD iterations after that (history). We are projecting a CR transition earliest Q4 2023.

As for the i18n review expectations, we'd like to get early indication if something is way off from an i18n perspective by the end of 2022 and hope to complete the full round of wide reviews during Q1 2023. Privacy is currently seen as an area where the WG has further work to do. As of now, we haven't identified any i18n considerations for this API.

I hope this helps clarify the expectations. Please reach out to me if you have any questions during your review journey and I will loop in relevant people from the WG to discuss any i18n topics further. Thank you for your time and effort.

[aphillips]

@anssiko Thanks. I may adjust our due date for the review after our teleconference of 2022-12-01 to sometime in January. Your group might also want to consider doing a self-review if your WG has cycles to spare (although it sounds like you've done something of the sort informally already)

[anssiko]

Sounds good. We did a self-review and its results are in w3c/window-management#118

[aphillips]

Issues submitted as of 2023-01-12. Thank you for your patience.

[anssiko]

@aphillips thank you!

Cross-referencing the i18n review issue here:
w3c/window-management#125
w3c/window-management#126
w3c/window-management#127

[aphillips]

Thanks @anssiko. Note that you can always find your issues collected in the horizontal review tracker

https://w3c.github.io/horizontal-issue-tracker/