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 On Thu, Apr 21, 2022 at 3:32 PM Jeremy Roman <[email protected]> wrote: > 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. > > On Thu, Apr 21, 2022 at 5:34 PM 'Ajay Rahatekar' via blink-dev < > [email protected]> wrote: > >> Hello blink-dev owners, >> >> The Chrome team is planning on implementing screen labels defined in the >> draft spec for Multi-Screen Window Placement >> <https://w3c.github.io/window-placement/#concept-screen>. The tracking >> bug for the implementation is here >> <https://bugs.chromium.org/p/chromium/issues/detail?id=1254885>. Can you >> please advise if we need an Intent email for shipping the implementation? >> The Multi-Screen Window Placement API shipped >> <https://chromestatus.com/feature/5252960583942144> 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 | [email protected] | >> 650-797-1279 <(650)%20650-797-1279> >> >> -- >> 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 [email protected]. >> 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 >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHB%2BDAhiEjBpHNF00toJvZR%2Bm3qfVEm3iyq%3DFGVO2Tj7AQ2PNA%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACuR13d2qfBzbJjWOrHFRjQHegqc-Fk%3Dp_kuTFVq4ygUAOJpmA%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACuR13d2qfBzbJjWOrHFRjQHegqc-Fk%3Dp_kuTFVq4ygUAOJpmA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw9zQFSzwXRpQ_E-VGGKOMrxtpixzpf0KOeo-Y8nHV7zJA%40mail.gmail.com.
