Intent to Experiment: Virtual keyboard API

156 views
Skip to first unread message

Keith Lee

unread,
Jun 17, 2021, 11:47:08 AMJun 17
to blin...@chromium.org

Contact emails

keit...@google.com

Explainer

https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/VirtualKeyboardAPI/explainer.md

Specification

None

Summary

JavaScript Web API to allow web developers to control the Virtual keyboard and format web pages based on the position of the virtual keyboard for the corresponding OS.



Blink component

Blink

TAG review

None

TAG review status

Not applicable

Risks



Interoperability and Compatibility

None



Gecko: No signal

WebKit: No signal

Web developers: No signals


Goals for experimentation

Get feedback on the API



Reason this experiment is being extended

None



Ongoing technical constraints

None



Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

No, it's currently supported on Windows we plan to provide ChromeOS support soon

Is this feature fully tested by web-platform-tests?

No

Flag name

VirtualKeyboard

Tracking bug

https://www.chromestatus.com/feature/5717448231747584

Launch bug

https://www.chromestatus.com/feature/5717448231747584

Link to entry on the Chrome Platform Status

https://www.chromestatus.com/feature/5717448231747584

This intent message was generated by Chrome Platform Status.

Joshua Bell

unread,
Jun 18, 2021, 2:46:41 PMJun 18
to Keith Lee, blin...@chromium.org
Exciting! Non-API owner drive-by, since I've been watching this one as an interested Fugu bystander and noticed the tracking bug wasn't linked.

On Thu, Jun 17, 2021 at 8:47 AM 'Keith Lee' via blink-dev <blin...@chromium.org> wrote:

Is all of the explainer implemented for the OT? i.e. both the new navigator.virtualKeyboard object and the CSS additions?
 


Specification

None

What's the plan here? Is anything blocking drafting a spec?
 


Summary

JavaScript Web API to allow web developers to control the Virtual keyboard and format web pages based on the position of the virtual keyboard for the corresponding OS.



Blink component

Blink

TAG review

None

TAG review status

Not applicable

Risks



Interoperability and Compatibility

None



Gecko: No signal

WebKit: No signal

Web developers: No signals


Goals for experimentation

Get feedback on the API



Reason this experiment is being extended

None



Ongoing technical constraints

None



Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

No, it's currently supported on Windows we plan to provide ChromeOS support soon

Is this feature fully tested by web-platform-tests?

No

The phrasing in the chromestatus template here doesn't help here... why "No" here? Is it partially tested by WPT, e.g. at least the IDL shape? Are there manual tests in WPT? Or is there a plan to add WPT coverage during the OT?
  


Flag name

VirtualKeyboard

Tracking bug

https://www.chromestatus.com/feature/5717448231747584

https://bugs.chromium.org/p/chromium/issues/detail?id=856269 I think? I updated the chromestatus entry, please fix if I picked the wrong one.

 


Launch bug

https://www.chromestatus.com/feature/5717448231747584

Link to entry on the Chrome Platform Status

https://www.chromestatus.com/feature/5717448231747584

This intent message was generated by Chrome Platform Status.

--
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/CAJFmwv8Jqa6eHAk0c_gWh_UhSWbEkQViD9x%2BNdupz4gDDA-ZoQ%40mail.gmail.com.

Yoav Weiss

unread,
Jun 21, 2021, 1:27:00 AMJun 21
to Joshua Bell, Keith Lee, blink-dev
On Fri, Jun 18, 2021 at 8:46 PM Joshua Bell <jsb...@chromium.org> wrote:
Exciting! Non-API owner drive-by, since I've been watching this one as an interested Fugu bystander and noticed the tracking bug wasn't linked.

On Thu, Jun 17, 2021 at 8:47 AM 'Keith Lee' via blink-dev <blin...@chromium.org> wrote:

Is all of the explainer implemented for the OT? i.e. both the new navigator.virtualKeyboard object and the CSS additions?
 


Specification

None

What's the plan here? Is anything blocking drafting a spec?

Note that a draft spec is required for an Origin Trial, in order to outline what you'd be experimenting with.

Mathias Bynens

unread,
Jun 21, 2021, 7:43:27 AMJun 21
to Keith Lee, blink-dev
The Intent* email template includes a “Debuggability” section, which is missing in this case. How would web developers debug this new functionality through DevTools? Do we need anything beyond existing DevTools functionality? See https://goo.gle/devtools-checklist for context.

--

Anupam Snigdha

unread,
Jun 21, 2021, 9:37:01 PMJun 21
to Mathias Bynens, Keith Lee, blink-dev, Bo Cupp, gl...@microsoft.com
Thank you Keith for implementing the VK API on ChromeOS and also sending I2E! Just wanted to chime in to help answer few questions in this thread.

TAG review

https://github.com/w3ctag/design-reviews/issues/498

https://github.com/w3ctag/design-reviews/issues/507


TAG review status

https://github.com/w3ctag/design-reviews/issues/498 -- Closed with resolution satisfied.
https://github.com/w3ctag/design-reviews/issues/507  -- Closed with ambivalent status.

Gecko: No signal (https://github.com/mozilla/standards-positions/issues/531)

WebKit: No signal (https://lists.webkit.org/pipermail/webkit-dev/2021-June/031878.html). We got a lot of feedback from WebKit devs throughout the design process. The TAG review threads have all the discussions so I think we do have positive support, but I'll wait for an explicit signal in the webkit thread.

Web developers: Positive
Signal from MS Office (https://github.com/w3ctag/design-reviews/issues/507#issuecomment-812766805)
Signal from Google docs (https://docs.google.com/document/d/1KtmXy9kGwADyP5x1tfLtGt8v86XetAiZwgcOTnDyTOY)
In the I2P thread few web devs also showed interest.


>  No, it's currently supported on Windows we plan to provide ChromeOS support soon

It's also supported on Android.

> The Intent* email template includes a “Debuggability” section, which is missing in this case. How would web developers debug this new functionality through DevTools?

The VK APIs that includes a new element attribute(virtualKeyboardpolicy), geometrychange JS event & CSS environment variables should have basic tooling support as described in the linked doc. Apart from that there is no support for web developers to debug system VK APIs through dev-tools.


> Note that a draft spec is required for an Origin Trial, in order to outline what you'd be experimenting with.

We are currently working on a spec and will send it out for review soon in the w3c/editing group.

-Anupam

Mathias Bynens

unread,
Jun 22, 2021, 1:32:09 AMJun 22
to Anupam Snigdha, Keith Lee, blink-dev, Bo Cupp, gl...@microsoft.com
On Tue, Jun 22, 2021 at 3:36 AM Anupam Snigdha <snianu.m...@gmail.com> wrote:
Thank you Keith for implementing the VK API on ChromeOS and also sending I2E! Just wanted to chime in to help answer few questions in this thread.

TAG review

https://github.com/w3ctag/design-reviews/issues/498

https://github.com/w3ctag/design-reviews/issues/507


TAG review status

https://github.com/w3ctag/design-reviews/issues/498 -- Closed with resolution satisfied.
https://github.com/w3ctag/design-reviews/issues/507  -- Closed with ambivalent status.

Gecko: No signal (https://github.com/mozilla/standards-positions/issues/531)

WebKit: No signal (https://lists.webkit.org/pipermail/webkit-dev/2021-June/031878.html). We got a lot of feedback from WebKit devs throughout the design process. The TAG review threads have all the discussions so I think we do have positive support, but I'll wait for an explicit signal in the webkit thread.

Web developers: Positive
Signal from MS Office (https://github.com/w3ctag/design-reviews/issues/507#issuecomment-812766805)
Signal from Google docs (https://docs.google.com/document/d/1KtmXy9kGwADyP5x1tfLtGt8v86XetAiZwgcOTnDyTOY)
In the I2P thread few web devs also showed interest.

>  No, it's currently supported on Windows we plan to provide ChromeOS support soon

It's also supported on Android.

> The Intent* email template includes a “Debuggability” section, which is missing in this case. How would web developers debug this new functionality through DevTools?

The VK APIs that includes a new element attribute(virtualKeyboardpolicy), geometrychange JS event & CSS environment variables should have basic tooling support as described in the linked doc. Apart from that there is no support for web developers to debug system VK APIs through dev-tools.

Sounds good. Please let us know if there’s any DevTools-specific questions we can help with.

Anupam Snigdha

unread,
Jun 22, 2021, 1:31:32 PMJun 22
to Mathias Bynens, Keith Lee, blink-dev, Bo Cupp, gl...@microsoft.com
Here is the PR of the draft spec: https://github.com/w3c/editing/pull/309

Anupam Snigdha

unread,
Jun 22, 2021, 1:51:19 PMJun 22
to Mathias Bynens, Keith Lee, blink-dev, Bo Cupp, gl...@microsoft.com
Sorry for multiple replies. I just noticed that there are two separate Chrome status entry for this feature. Should we update https://www.chromestatus.com/guide/edit/5680057076940800 since it was used in the i2p process? 

Manuel Rego Casasnovas

unread,
Jun 23, 2021, 3:56:34 AMJun 23
to Anupam Snigdha, Mathias Bynens, Keith Lee, blink-dev, Bo Cupp, gl...@microsoft.com


On 22/06/2021 19:51, Anupam Snigdha wrote:
> Sorry for multiple replies. I just noticed that there are two
> separate Chrome status entry for this feature. Should we
> update https://www.chromestatus.com/guide/edit/5680057076940800
> <https://www.chromestatus.com/guide/edit/5680057076940800> since it was
> used in the i2p process?

Yeah there should be just one entry in chromestatus, so you need to
remove one of these 2:
* https://www.chromestatus.com/feature/5680057076940800
* https://www.chromestatus.com/feature/5717448231747584

And then update the content there as it goes through the different phases.

Cheers,
Rego

>
> On Tue, Jun 22, 2021 at 10:31 AM Anupam Snigdha
> <snianu.m...@gmail.com <mailto:snianu.m...@gmail.com>> wrote:
>
> Here is the PR of the draft
> spec: https://github.com/w3c/editing/pull/309
> <https://github.com/w3c/editing/pull/309>
>
> On Mon, Jun 21, 2021 at 10:32 PM Mathias Bynens <mt...@google.com
> <mailto:mt...@google.com>> wrote:
>
>
>
> On Tue, Jun 22, 2021 at 3:36 AM Anupam Snigdha
> <snianu.m...@gmail.com <mailto:snianu.m...@gmail.com>>
> wrote:
>
> Thank you Keith for implementing the VK API on ChromeOS and
> also sending I2E! Just wanted to chime in to help answer few
> questions in this thread.
>
> i2p: https://groups.google.com/a/chromium.org/g/blink-dev/c/q80uCrMgiTM/m/nF3mo-7zBAAJ
> <https://groups.google.com/a/chromium.org/g/blink-dev/c/q80uCrMgiTM/m/nF3mo-7zBAAJ>
>
> *TAG review*____
>
> https://github.com/w3ctag/design-reviews/issues/498
> <https://github.com/w3ctag/design-reviews/issues/498>____
>
> https://github.com/w3ctag/design-reviews/issues/507
> <https://github.com/mozilla/standards-positions/issues/531>)
>
> WebKit: No signal
> (https://lists.webkit.org/pipermail/webkit-dev/2021-June/031878.html
> <https://lists.webkit.org/pipermail/webkit-dev/2021-June/031878.html>).
> We got a lot of feedback from WebKit devs throughout the
> design process. The TAG review threads have all the
> discussions so I think we do have positive support, but I'll
> wait for an explicit signal in the webkit thread.
>
> Web developers: Positive
> Signal from MS Office
> (https://github.com/w3ctag/design-reviews/issues/507#issuecomment-812766805
> <https://github.com/w3ctag/design-reviews/issues/507#issuecomment-812766805>)
> <https://docs.google.com/document/d/1KtmXy9kGwADyP5x1tfLtGt8v86XetAiZwgcOTnDyTOY>)
> In the I2P thread few web devs also showed interest.
>
> >  No, it's currently supported on Windows we plan to
> provide ChromeOS support soon
>
> It's also supported on Android.
>
> > The Intent* email template includes a “Debuggability”
> section, which is missing in this case. How would web
> developers debug this new functionality through DevTools?
>
> The VK APIs that includes a new element
> attribute(virtualKeyboardpolicy), geometrychange JS event &
> CSS environment variables should have basic tooling support
> as described in the linked doc. Apart from that there is no
> support for web developers to debug system VK APIs through
> dev-tools.
>
>
> Sounds good. Please let us know if there’s any DevTools-specific
> questions we can help with.
>  
>
> > Note that a draft spec is required
> <https://www.chromium.org/blink/origin-trials/running-an-origin-trial#:~:text=Have%20a%20draft%20spec%20for%20your%20feature> for
> an Origin Trial, in order to outline what you'd be
> experimenting with.
>
> We are currently working on a spec and will send it out for
> review soon in the w3c/editing
> <https://github.com/w3c/editing> group.
>
> -Anupam
>
> On Mon, Jun 21, 2021 at 4:43 AM 'Mathias Bynens' via
> blink-dev <blin...@chromium.org
> <mailto:blin...@chromium.org>> wrote:
>
> The Intent* email template includes a “Debuggability”
> section, which is missing in this case. How would web
> developers debug this new functionality through
> DevTools? Do we need anything beyond existing DevTools
> functionality? See https://goo.gle/devtools-checklist
> <https://goo.gle/devtools-checklist> for context.
>
> On Thu, Jun 17, 2021 at 5:47 PM 'Keith Lee' via
> blink-dev <blin...@chromium.org
> <mailto:blin...@chromium.org>> wrote:
>
>
> Contact emails
>
> keit...@google.com <mailto:keit...@google.com>
>
>
> Explainer
>
> https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/VirtualKeyboardAPI/explainer.md
> <https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/VirtualKeyboardAPI/explainer.md>
>
>
> Specification
>
> None
>
>
> Summary
>
> JavaScript Web API to allow web developers to
> control the Virtual keyboard and format web pages
> based on the position of the virtual keyboard for
> the corresponding OS.
> <https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/VirtualKeyboardAPI/explainer.md>
>
>
>
> Blink component
>
> Blink
> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink>
>
>
> TAG review
>
> None
>
>
> TAG review status
>
> Not applicable
>
>
> Risks
>
>
>
> Interoperability and Compatibility
>
> None
>
>
>
> Gecko: No signal
>
> WebKit: No signal
>
> Web developers: No signals
>
>
> Goals for experimentation
>
> Get feedback on the API
>
>
>
> Reason this experiment is being extended
>
> None
>
>
>
> Ongoing technical constraints
>
> None
>
>
>
> Will this feature be supported on all six
> Blink platforms (Windows, Mac, Linux, Chrome
> OS, Android, and Android WebView)?
>
> No, it's currently supported on Windows we plan to
> provide ChromeOS support soon
>
>
> Is this feature fully tested
> by web-platform-tests
> <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md>?
>
> No
>
>
> Flag name
>
> VirtualKeyboard
>
>
> Tracking bug
>
> https://www.chromestatus.com/feature/5717448231747584 <https://www.chromestatus.com/feature/5717448231747584>
>
>
> Launch bug
>
> https://www.chromestatus.com/feature/5717448231747584 <https://www.chromestatus.com/feature/5717448231747584>
>
>
> Link to entry on the Chrome Platform Status
>
> https://www.chromestatus.com/feature/5717448231747584 <https://www.chromestatus.com/feature/5717448231747584>
>
> This intent message was generated by Chrome Platform
> Status <https://www.chromestatus.com/>.
>
> --
> 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
> <mailto:blink-dev+...@chromium.org>.
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJFmwv8Jqa6eHAk0c_gWh_UhSWbEkQViD9x%2BNdupz4gDDA-ZoQ%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
> blink-dev+...@chromium.org
> <mailto:blink-dev+...@chromium.org>.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADizRgZsgBns9ok4aayC5X9uH%3D_vxUFTedNwbXUJgWbZTLpydA%40mail.gmail.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADizRgZsgBns9ok4aayC5X9uH%3D_vxUFTedNwbXUJgWbZTLpydA%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 blink-dev+...@chromium.org
> <mailto:blink-dev+...@chromium.org>.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2Bm%3DdJqaPHp2bOtJrjHuWfRHqMHtva22UQb7iZNBOWBNxWnCCQ%40mail.gmail.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2Bm%3DdJqaPHp2bOtJrjHuWfRHqMHtva22UQb7iZNBOWBNxWnCCQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.

Yoav Weiss

unread,
Jun 24, 2021, 12:16:30 PMJun 24
to blink-dev, snianu.m...@gmail.com, keit...@google.com, blink-dev, Bo Cupp, glyu...@gmail.com, Mathias Bynens
Thank you!! Setting up PR-preview for that would be extremely helpful and make it easier to review.

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

--
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+unsubscribe@chromium.org.

Yoav Weiss

unread,
Jun 25, 2021, 9:12:23 AMJun 25
to blink-dev, Yoav Weiss, snianu.m...@gmail.com, keit...@google.com, blink-dev, Bo Cupp, glyu...@gmail.com, Mathias Bynens
One last detail I'm missing: what's the timeline for the experimentation?



On Thursday, June 24, 2021 at 6:16:30 PM UTC+2 Yoav Weiss wrote:
Thank you!! Setting up PR-preview for that would be extremely helpful and make it easier to review.

I've applied the PR locally to review it in the interim. I was helpful for me to understand the expected flow, so thanks for writing it :)
I left a few comments on the PR. I also found a few discrepancies between it and the explainer (e.g. the `show()` and `hide()` methods are not in the explainer).
Would be good to align both documents to say the same thing. Another inconsistency that would be good to clarify before asking developers to write code against this is whether these methods return promises or not.

Anupam Snigdha

unread,
Jun 25, 2021, 1:49:59 PMJun 25
to Yoav Weiss, blink-dev, keit...@google.com, Bo Cupp, glyu...@gmail.com, Mathias Bynens
Thank you for reviewing the PR, Yoav! I'll work with Grisha and address all your comments. Also, yes, I noticed that `show` & `hide` APIs are not well described so I'll add more info to the explainer.

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

--
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.

Mike West

unread,
Jul 1, 2021, 2:30:26 PMJul 1
to Anupam Snigdha, Yoav Weiss, blink-dev, keit...@google.com, Bo Cupp, glyu...@gmail.com, Mathias Bynens
Yoav asked about the timeline, but y'all didn't respond.

To avoid another round-trip: assuming this is a typical 3-milestone experiment starting in M93, LGTM to experiment. If you have needs that go beyond that timeframe, let's chat!

-mike


Domenic Denicola

unread,
Jul 1, 2021, 3:02:53 PMJul 1
to Mike West, Anupam Snigdha, Yoav Weiss, blink-dev, keit...@google.com, Bo Cupp, glyu...@gmail.com, Mathias Bynens

FWIW this has occurred on a lot of emails recently. I suspect ChromeStatus is not outputting or asking for this field…

Jeffrey Yasskin

unread,
Jul 1, 2021, 3:43:21 PMJul 1
to Domenic Denicola, Mike West, Anupam Snigdha, Yoav Weiss, blink-dev, keit...@google.com, Bo Cupp, glyu...@gmail.com, Mathias Bynens
When you notice problems with Chrome Status, you can file them at https://github.com/GoogleChrome/chromium-dashboard/issues, which is linked from the very bottom of https://chromestatus.com/.

Marijn Kruisselbrink

unread,
Jul 1, 2021, 5:15:59 PMJul 1
to Jeffrey Yasskin, Domenic Denicola, Mike West, Anupam Snigdha, Yoav Weiss, blink-dev, keit...@google.com, Bo Cupp, glyu...@gmail.com, Mathias Bynens
On Thu, Jul 1, 2021 at 12:43 PM Jeffrey Yasskin <jyas...@chromium.org> wrote:
When you notice problems with Chrome Status, you can file them at https://github.com/GoogleChrome/chromium-dashboard/issues, which is linked from the very bottom of https://chromestatus.com/.

This particular issue has been filed several times, I think https://github.com/GoogleChrome/chromium-dashboard/issues/1162 is the canonical issue (and has been open for almost 6 months) 

 

Anupam Snigdha

unread,
Jul 1, 2021, 7:35:21 PMJul 1
to Marijn Kruisselbrink, Jeffrey Yasskin, Domenic Denicola, Mike West, Yoav Weiss, blink-dev, keit...@google.com, Bo Cupp, glyu...@gmail.com, Mathias Bynens, Anupam Snigdha
Sorry Mike, I completely missed that question! Actually I'm not really sure what the plan is as I think this API is ready to ship. I'm working on adding wpt tests and Grisha is working on the draft spec. We've filed request for support from mozilla and apple and also have strong web developer signals for this API: https://github.com/w3c/editing/issues/308
I'll wait for Keith to reply to the experiment timeline, but I was planning to send an intent to ship soon once we have everything sorted out.

-Anupam

Keith Lee

unread,
Jul 2, 2021, 1:28:01 AMJul 2
to Anupam Snigdha, Marijn Kruisselbrink, Jeffrey Yasskin, Domenic Denicola, Mike West, Yoav Weiss, blink-dev, Bo Cupp, glyu...@gmail.com, Mathias Bynens, Anupam Snigdha
Hi All,

Sorry about the delays in responding.

I wanted to do an origin trial for M93-96 in ChromeOS to collect dev feedback, since it's hard to change APIs after they are shipped. That way developers who want to try the API early can sign up for the origin trial and we can account for feedback from devs whom have not responded yet.

@Anupam Snigdha  What else needs to be sorted out before sending out I2S?

-Keith
--
Yours Sincerely,
Keith

Anupam Snigdha

unread,
Jul 2, 2021, 2:53:35 AMJul 2
to keit...@google.com, snianu.m...@gmail.com, m...@chromium.org, jyas...@chromium.org, d...@domenic.me, mk...@chromium.org, yoav...@chromium.org, blin...@chromium.org, Bo Cupp, Grisha Lyukshin, mt...@google.com
Hi Keith, 

We need to merge the draft spec for the VK API into the editing repo and then I'll submit the CL containing the wpt tests. I'm having some issues with idlharness.https.window.html tests(https://chromium-review.googlesource.com/c/chromium/src/+/2993938) so I'm still trying to figure out the fix for that. We did an origin trial in Edge and addressed all feedback from Excel online team, so we wanted them to post their support in the public github issue. I guess we have sufficient developer signals so probably we can send I2S without waiting for more developer support/feedback. 

-Anupam

From: Keith Lee <keit...@google.com>
Sent: Thursday, July 1, 2021 10:27 PM
To: Anupam Snigdha <snianu.m...@gmail.com>
Cc: Marijn Kruisselbrink <m...@chromium.org>; Jeffrey Yasskin <jyas...@chromium.org>; Domenic Denicola <d...@domenic.me>; Mike West <mk...@chromium.org>; Yoav Weiss <yoav...@chromium.org>; blink-dev <blin...@chromium.org>; Bo Cupp <pc...@microsoft.com>; Grisha Lyukshin <Grisha....@microsoft.com>; Mathias Bynens <mt...@google.com>; Anupam Snigdha <sni...@microsoft.com>
Subject: [EXTERNAL] Re: [blink-dev] Intent to Experiment: Virtual keyboard API
 

Grisha Lyukshin

unread,
Jul 2, 2021, 1:37:34 PMJul 2
to Anupam Snigdha, keit...@google.com, snianu.m...@gmail.com, m...@chromium.org, jyas...@chromium.org, d...@domenic.me, mk...@chromium.org, yoav...@chromium.org, blin...@chromium.org, Bo Cupp, mt...@google.com
A couple of questions to the group just so we know how to proceed. 

Keith, is your preference to run VK API origin trials first? If so, we'll have to wait to send an i2s.

If you are ok with going straight to i2s then question for blink-dev: is it ok if repurpose this thread from i2e -> i2s given that Edge has ran origin trials on this already? 

Thanks,
Grisha

From: Anupam Snigdha <sni...@microsoft.com>
Sent: Thursday, July 1, 2021 11:53 PM
To: Keith Lee <keit...@google.com>; Anupam Snigdha <snianu.m...@gmail.com>

Cc: Marijn Kruisselbrink <m...@chromium.org>; Jeffrey Yasskin <jyas...@chromium.org>; Domenic Denicola <d...@domenic.me>; Mike West <mk...@chromium.org>; Yoav Weiss <yoav...@chromium.org>; blink-dev <blin...@chromium.org>; Bo Cupp <pc...@microsoft.com>; Grisha Lyukshin <Grisha....@microsoft.com>; Mathias Bynens <mt...@google.com>
Subject: Re: [EXTERNAL] Re: [blink-dev] Intent to Experiment: Virtual keyboard API
 

Yoav Weiss

unread,
Jul 7, 2021, 2:16:01 AMJul 7
to Grisha Lyukshin, Anupam Snigdha, keit...@google.com, snianu.m...@gmail.com, m...@chromium.org, jyas...@chromium.org, d...@domenic.me, mk...@chromium.org, blin...@chromium.org, Bo Cupp, mt...@google.com
I'll let Keith answer the question on running a Chrome OT, given Edge's OT experience.

From a process perspective, it'd be better to file a new I2S if y'all decide to go towards shipping directly. For the purpose of an I2S, I think it may be useful to summarize and publish the OT results.

Anupam Snigdha

unread,
Jul 26, 2021, 4:53:49 PMJul 26
to Yoav Weiss, Grisha Lyukshin, Anupam Snigdha, keit...@google.com, m...@chromium.org, jyas...@chromium.org, d...@domenic.me, mk...@chromium.org, blin...@chromium.org, Bo Cupp, mt...@google.com
Hi All,

Discussed this with Keith in a separate thread and we decided to go ahead with I2S instead of OT. I added Edge’s OT feedback in the I2S for more data. It mainly contains the feedback that we received from developers who are currently using the API that helped us make improvements in the API design.
Please let me know in case of any concerns.

Thanks,
Anupam

Keith Lee

unread,
Jul 28, 2021, 5:08:01 AMJul 28
to Anupam Snigdha, Yoav Weiss, Grisha Lyukshin, Anupam Snigdha, m...@chromium.org, jyas...@chromium.org, d...@domenic.me, mk...@chromium.org, blin...@chromium.org, Bo Cupp, mt...@google.com
Since an Edge OT has been run, we are planning on skipping the OT for Chrome, since we've already gotten dev feedback for the current spec, and filing a separate I2S later on.
--
Yours Sincerely,
Keith
Reply all
Reply to author
Forward
0 new messages