Re: [w3c/editing] JS API to invoke native desktop emoji picker (#350)

Per the [minutes above](https://github.com/w3c/editing/issues/350#issuecomment-954891077) I'm summarizing some issues that we'd like to see addressed in a concrete API proposal. It would be appreciated if someone could put forth such a proposal so we could consider it in a future WG meeting.  Additionally, it seems clear that a thorough survey of existing emoji input mechanisms across platforms would be a helpful input when considering the fitness of any particular design.  If someone is also willing to create that it would be much appreciated.

* On MacOS, there are two modes for the emoji picker window: a transient mode used while editing where it appears near the caret, and another where it appears in a persistent manner when not editing or when dragged away from the caret.  How should these two states impact the API?
* On some platforms like Linux, for example, an emoji picker may not be available.  Should there be an API to detect whether or not an emoji picker is supported so that the site could author other affordances if not?
* Virtual Keyboards on Windows have an emoji inputMode which is separate from the emoji picker.  Should there be an extension to the Virtual Keyboard API to specify an inputMode, e.g. `navigator.virtualKeyboard.show({inputMode: "emoji"})`.
*  On iOS I think the only emoji picker is the one built into the Virtual Keyboard.  Would that require the API enhancement to the VirtualKeyboard interface mentioned above or should that inputMode be what is revealed when the author invokes this new API to show the emoji picker?
* Lastly there was mention of an `<input type="emoji">` in [this discourse thread](https://discourse.wicg.io/t/invoke-emoji-input/1030/9).  We should make sure that any API we create doesn't require loss of focus for scenarios where the user wants to type an emoji in an existing text input field.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/350#issuecomment-955069588