Request for Guidance

52 views
Skip to first unread message

Ajay Rahatekar

unread,
Apr 21, 2022, 5:34:56 PM4/21/22
to blink-dev, Mike Wasserman, Ben Morss
Hello blink-dev owners,

The Chrome team is planning on implementing screen labels defined in the draft spec for Multi-Screen Window Placement. The tracking bug for the implementation is here. Can you please advise if we need an Intent email for shipping the implementation? The Multi-Screen Window Placement API shipped in Chrome M100.

Please excuse and guide if this is not the appropriate forum for this request.

Thanks in advance.


--
Ajay Rahatekar | Technical Program Manager | ajayra...@google.com | 650-797-1279

Jeremy Roman

unread,
Apr 21, 2022, 6:32:36 PM4/21/22
to Ajay Rahatekar, blink-dev, Mike Wasserman, Ben Morss
I'm not an API owner, but since it's shipped already I would suggest you just do an Intent to Prototype & Ship. If it's a relatively small feature then hopefully it will also be relatively quick for API owners to review.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHB%2BDAhiEjBpHNF00toJvZR%2Bm3qfVEm3iyq%3DFGVO2Tj7AQ2PNA%40mail.gmail.com.

Chris Harrelson

unread,
Apr 21, 2022, 8:01:32 PM4/21/22
to Jeremy Roman, Ajay Rahatekar, blink-dev, Mike Wasserman, Ben Morss
Hi Ajay,

Every new web-exposed feature, even if it's a small addition to an existing API, needs an intent to ship. This helps us make sure that all new features are tracked and understood by the community, and have the right level of open standards engagement, consensus and so on. Also, it happens surprisingly often that a feature that looks very simple ends up being more complicated than it looks, and the intent is one way to find out those complications before shipping so we can address them.

If you consider this a very simple feature add-on, I recommend re-using the existing TAG review with a new comment on it, and also comments on the existing signals to other vendors from the prior intent. If you choose to do that, the API owners will in their review let you know if for some reason we feel it's a good idea to open an new TAG review or take some other step.

Thanks,
Chris

Ajay Rahatekar

unread,
Apr 22, 2022, 9:34:13 AM4/22/22
to Chris Harrelson, Jeremy Roman, blink-dev, Mike Wasserman, Ben Morss
Ty Jeremy and Chris for the great responses and guidance. Much appreciated.

-Ajay
Reply all
Reply to author
Forward
0 new messages