Coming back to the intent-to-ship part: do you consider it ready for
approval? Or are there more spec or other issues to iron out before we
should consider approval?

On Thu, Dec 9, 2021 at 9:50 PM Chris Harrelson <[email protected]>
wrote:

> I think it's ok. LGTM. Thanks for doing your best to ship a high-quality
> implementation!
>
> Note that this will be a total of 8 milestones
> <https://groups.google.com/a/chromium.org/g/blink-dev/c/NALmrt8Qmgg/m/BtrH5eTMAQAJ>,
> including M98, but as was mentioned in a previous intent, there was also a
> breaking API change in M95, plus evidence of experimental feedback.
>
> On Wed, Dec 8, 2021 at 9:07 PM Glen Robertson <[email protected]>
> wrote:
>
>> Given that the Handwriting Recognition OT ends with M97, and M98 branches
>> today, it seems like it will be difficult to ship in M98 - a merge request
>> to enable the feature is unlikely to be approved.
>>
>> 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 <[email protected]> wrote:
>>
>>> Contact emails
>>>
>>> [email protected], [email protected], [email protected]
>>>
>>> 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/blob/main/explainer.md
>>>
>>> Summary
>>>
>>> An API for web applications to make use of advanced handwriting
>>> recognition services (e.g. those on operating systems) to recognize text
>>> from handwriting drawings (inks) in real time. In this context, handwriting
>>> drawing means the temporal and positional information used to describe a
>>> human handwriting process.
>>>
>>>
>>> Blink component
>>>
>>> Blink>Handwriting
>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EHandwriting>
>>>
>>> TAG review
>>>
>>> https://github.com/w3ctag/design-reviews/issues/591
>>>
>>> TAG review status
>>>
>>> Issues addressed
>>>
>>> Link to origin trial feedback summary
>>>
>>>
>>> https://docs.google.com/document/d/1BGd3WiwiqBA1JQaG-r0bc5No0f0KkqW13EhO1YeQocA/edit
>>>
>>> Risks
>>>
>>> Interoperability and Compatibility
>>>
>>> Different browsers (and operating systems) will expose different
>>> underlying implementations and produce different outputs given the same
>>> input. We think this is acceptable given the implementation is
>>> machine-learning based, and it is not feasible or desirable to precisely
>>> specify the expected output for a given input in a standard. In the past,
>>> we have taken this approach for the Web Speech and Shape Detection APIs.
>>>
>>>
>>> Gecko: No signal (
>>> https://github.com/mozilla/standards-positions/issues/507) Feedback
>>> requested, no reply yet.
>>>
>>> WebKit: No signal (
>>> https://lists.webkit.org/pipermail/webkit-dev/2021-March/031762.html)
>>> Feedback requested, no reply yet.
>>>
>>> Web developers: Positive (
>>> https://github.com/WICG/handwriting-recognition/issues/21) Twitter:
>>> https://twitter.com/ChromiumDev/status/1428640785810051074
>>>
>>> Other signals:
>>>
>>>
>>> Debuggability
>>>
>>> N/A. Existing DevTools tooling works for this feature.
>>>
>>>
>>> Is this feature fully tested by web-platform-tests
>>> <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md>
>>> ?
>>>
>>> No. Full coverage relies on platform-specific implementation. WPT only
>>> tests failure cases.
>>>
>>> Flag name
>>>
>>> Requires code in //chrome?
>>>
>>> False
>>>
>>> Tracking bug
>>>
>>> https://crbug.com/1207667
>>>
>>> Launch bug
>>>
>>> https://crbug.com/1206121
>>>
>>> Estimated milestones
>>>
>>> OriginTrial desktop last
>>>
>>> 97
>>>
>>> OriginTrial desktop first
>>>
>>> 91
>>>
>>>
>>>
>>>
>>> Link to entry on the Chrome Platform Status
>>>
>>> https://chromestatus.com/feature/5263213807534080
>>>
>>> Links to previous Intent discussions
>>>
>>> Intent to prototype:
>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/VXUq1UY4m7Y
>>>
>>> Intent to Experiment:
>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/o8RqlFwZItQ/m/vgHLF_pHBQAJ
>>>
>>>
>>> This intent message was generated by Chrome Platform Status
>>> <https://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 [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPV%2BSg-5XE4cpDbwT69_T4u2CPN18O-9y_8nAW%2Bq-XYpwtjn3A%40mail.gmail.com
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPV%2BSg-5XE4cpDbwT69_T4u2CPN18O-9y_8nAW%2Bq-XYpwtjn3A%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%2Bw9XKeNj0Vznbv7bz_O%2BqvstWn89GOaO1xrzbe2XnDB8%2Bw%40mail.gmail.com.

Reply via email to