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?
Looking at the blink-api-owners-discuss thread, I see a focus on
getting more clear vendor signals as well as notifying everyone earlier
with an Intent to Prototype email.
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.
--
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/2ba106df-bb46-efac-dfa2-d4d86299e366%40intel.com.
