the process dictates a gap is to remove the
>> pressure to ship an imperfect API. For us to consider a gap-less shipping
>> we therefore want to be sure that feedback has been taken into account and
>> incorporated into the API. Can you point to such examples?
>>
>> /D
allow enough time for users to update.
The API shipped in M99 is the same as the one under origin trial.
Thanks for considering.
On Tue, Jan 4, 2022 at 6:36 AM Chris Harrelson
wrote:
> LGTM
>
> On Tue, Dec 21, 2021 at 7:33 PM Jiewei Qian wrote:
>
>> Contact emails...@ch
d be great to have a list in this
>> thread of the bits that will be closed-source and potentially diverge by
>> platform. Thanks!"
>>
>> LGTM2 from me, but please reply with the bits Alex mentioned thanks.
>>
>> On Wed, Dec 22, 2021 at 5:02 PM Jiewei Qian
ser's language settings and
preferences.
On Tue, Dec 21, 2021 at 3:38 PM Jiewei Qian wrote:
> The spec is currently being reviewed by the spec mentor. Otherwise we
> think the feature is ready for review.
>
> On Thu, Dec 16, 2021 at 3:57 AM Chris Harrelson
> wrote:
>
Contact emails...@chromium.org, hongli...@chromium.org, mgi...@chromium.org
Explainer
https://github.com/WICG/handwriting-recognition/blob/main/explainer.md
Specificationhttps://wicg.github.io/handwriting-recognition/
Design docs
https://github.com/WICG/handwriting-recognition/blob/main/explaine
>
>>> Blink Owners: Would it be acceptable to extend the OT for 1 additional
>>> milestone (end in M98) and ship in M99?
>>>
>>> On Thu, 9 Dec 2021 at 02:57, Jiewei Qian wrote:
>>>
>>>> Contact emails
>>>>
>>>> q...@
Contact emails
q...@chromium.org, hongli...@chromium.org, mgi...@chromium.org
Explainer
https://github.com/WICG/handwriting-recognition/blob/main/explainer.md
Specification
https://wicg.github.io/handwriting-recognition/ [in review]
Design docs
https://github.com/WICG/handwriting-recognition
Hi blink-dev,
Our Handwriting Recognition API origin trial ends in M97. M98 branches in a
week.
We want to get some recommendations on shipping vs continuing experimenting.
At the moment:
-
We have just 1 app using the origin trial (based on received feedback),
so there is little risk
at 12:26 AM Yoav Weiss wrote:
>
>
> On Monday, August 23, 2021 at 8:43:49 AM UTC+2 Thomas Steiner wrote:
>
>> On Mon, Aug 23, 2021 at 5:45 AM Jiewei Qian wrote:
>>
>>> Contact emails...@chromium.org, hongli...@chromium.org,
>>> mgi...@chromium.org
>>
-dev@chromium.org>:
>>
>>> As the co-author of the article about the feature
>>> <https://web.dev/handwriting-recognition/> I find the namespaced
>>> variant more logical and more in-line with how other APIs work, for
>>> example, Geolocation
&
Hi blink-dev,
We are designing a new API for handwriting recognition, and want to know if
we should put methods behind a namespace.
We have two methods:
- navigator.queryHandwritingRecognizerSupport
- navigator.createHandwritingRecognizer
We anticipate most websites will call the first me
Contact emails...@chromium.org, hongli...@chromium.org, mgi...@chromium.org
Explainer
https://github.com/WICG/handwriting-recognition/blob/main/explainer.md
Specification
Summary
An API for web applications to make use of advanced handwriting recognition
services (e.g. those on operating system
12 matches
Mail list logo
