Thanks for the feedback. I should have been more clear with
the terminology.
Seems navigator.handwriting.{create, query}Recognizer is preferred.
Other APIs also use this pattern (e.g. navigator.usb, navigator.bluetooth,
navigator.geolocation).
> Web IDL namespaces
Thanks for Yuki's explanation. Our API can change states (e.g. it needs to
create a recognizer in the browser), so Web IDL namespace isn't a good fit.
> Double nesting
I'm a bit hesitant about adding a new global / window scoped object, as it
could interfere with existing code (e.g. when JS defines a global
handwriting variable by itself). Putting it behind the navigator object is
more robust.
Also, handwriting recognition capability is provided (and varies) by the
browser, so it would make sense to put it on the navigator object.
On Wed, Aug 25, 2021 at 1:13 AM Domenic Denicola <dome...@chromium.org>
wrote:
> I would suggest *not* doubly-nesting. I.e.
> handwriting.queryRecognizerSupport, not
> navigator.handwriting.queryRecognizerSupport.
>
> And, using a proper namespace might indeed be best here.
>
> On Tue, Aug 24, 2021 at 3:05 AM Yuki Shiino <yukishi...@chromium.org>
> wrote:
>
>> Just as an input, Web IDL supports "namespace", which is different from a
>> namespace-ish object.
>>
>> Example)
>> https://drafts.csswg.org/cssom/#the-css.escape()-method
>> CSS namespace appears as "window.CSS" in JavaScript.
>>
>> "window.navigator" is a (singleton) instance of Navigator interface
>> (hence the object can be stateful) and not a namespace (which is stateless).
>>
>> It's a convention that Web IDL namespace's name starts with an uppercase
>> (window.CSS) while Web IDL attribute's name starts with a lowercase
>> (window.navigator). Web IDL namespaces are exposed on global objects (like
>> "window.CSS").
>>
>> Cheers,
>> Yuki Shiino
>>
>>
>> 2021年8月24日(火) 15:40 'Thomas Steiner' via blink-dev <
>> blink-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
>>> <https://developer.mozilla.org/en-US/docs/Web/API/Geolocation>. (Not a
>>> big argument: It also allows for better minification.)
>>>
>>> On Tue, Aug 24, 2021 at 6:44 AM Jiewei Qian <q...@chromium.org> wrote:
>>>
>>>> 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 method (to decide if
>>>> the handwriting recognition support meets their needs), before calling the
>>>> second (to make use of the feature).
>>>>
>>>> We want to know if it's more preferable to put them behind a namespace,
>>>> for example:
>>>>
>>>> - navigator.handwriting.queryRecognizerSupport
>>>> - navigator.handwriting.createRecognizer
>>>>
>>>>
>>>> --
>>>> 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+unsubscr...@chromium.org.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CANFkJJ%3DdX_DHHo2fSNJPL1DT5zGnuQYKGfjeHekrbcRE4E%2Bo6w%40mail.gmail.com
>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CANFkJJ%3DdX_DHHo2fSNJPL1DT5zGnuQYKGfjeHekrbcRE4E%2Bo6w%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>
>>>
>>> --
>>> Thomas Steiner, PhD—Developer Advocate (https://blog.tomayac.com,
>>> https://twitter.com/tomayac)
>>>
>>> Google Germany GmbH, ABC-Str. 19, 20354 Hamburg, Germany
>>> <https://www.google.com/maps/search/ABC-Str.+19,+20354+Hamburg,+Germany?entry=gmail&source=g>
>>> Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
>>> Registergericht und -nummer: Hamburg, HRB 86891
>>>
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v2.1.23 (GNU/Linux)
>>>
>>>
>>> iFy0uwAntT0bE3xtRa5AfeCheCkthAtTh3reSabiGbl0ck0fjumBl3DCharaCTersAttH3b0ttom.
>>> hTtPs://xKcd.cOm/1181/
>>> -----END PGP SIGNATURE-----
>>>
>>> --
>>> 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+unsubscr...@chromium.org.
>>> To view this discussion on the web visit
>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALgRrLm16Bhv88nz4Yts999890b4kbDdKmGJVcJxCiSVYtY%3DsQ%40mail.gmail.com
>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALgRrLm16Bhv88nz4Yts999890b4kbDdKmGJVcJxCiSVYtY%3DsQ%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+unsubscr...@chromium.org.
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAN0uC_S901%2BzrvHC_wuQKqMSmvcC%3DSX9xijweyr8X_NhW%2BJj-g%40mail.gmail.com
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAN0uC_S901%2BzrvHC_wuQKqMSmvcC%3DSX9xijweyr8X_NhW%2BJj-g%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+unsubscr...@chromium.org.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM0wra_DJ267NhiZVRW3xjVCYotxQQ2rXF4s%3DZQc8TZ8tQy5fw%40mail.gmail.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM0wra_DJ267NhiZVRW3xjVCYotxQQ2rXF4s%3DZQc8TZ8tQy5fw%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+unsubscr...@chromium.org.
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CANFkJJn0H9whHnpHmtCTBFyGs2Rg7tF1%2Bz0nnYSWn9pWiDtKgQ%40mail.gmail.com.
