On Wed, Jun 7, 2023 at 9:30 AM Raphael Kubo da Costa <
[email protected]> wrote:

> Op 31-05-2023 om 20:44 schreef Chris Harrelson:
> > TL;DR: going forward, new WebDriver Classic and WebDriver BiDi APIs in
> > Chromium need to go through the Intent process, including in particular
> > Intent to Prototype and Intent to Ship.
> >
> > See here
> > <
> https://groups.google.com/a/chromium.org/g/blink-api-owners-discuss/c/SYA56RETDGc/m/yicXrX3qAAAJ>
> for a more detailed description of and motivation for the changes.
>
> Hi Chris,
>
> Could you elaborate on how the Intent process would apply in terms of
> timelines and if some equivalent of a runtime flag would be required?
>

There are no minimum or maximum amounts of time required before shipping.
Just like with other features, landing code for a new feature requires an
Intent to Prototype before doing so, and likewise an Intent to Experiment
or Intent to Ship is needed before an origin trial or shipping.

What's unclear to me is whether there's also supposed to be a minimum
> amount of time/milestones between an Intent to Prototype and an Intent
> to Ship in this case, and also what the difference between an I2P and an
> I2S would be here, as there doesn't seem to be a way to gate new
> ChromeDriver endpoints and commands behind a flag.
>

If that's true it needs to be fixed. Flag-guarding features is a critically
necessary aspect of development best practices for Chromium features, to
allow them the time to be implemented incrementally, and also to be turned
off if new features cause regressions in the wild. @Mathias Bynens
<[email protected]>, could you advise on how to add runtime flags for
WebDriver?

Thanks,
Chris

-- 
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%2Bw-ffhRRVFbnQ%3DWC9quV7eEuGP2w%3D9NBVdvLWyYxmGiSgw%40mail.gmail.com.

Reply via email to