Confirm
716
edits
Changes
→Proposed API
// [Tim] I don't think they are exclusive. A keyboard app might choose to load the same page with the same hash
// for different types but only to deal with the |type| or |inputmode| difference later.
// [JS] I agree that exposing type etc is a good idea. It's quite likely that the same keyboard
// app will want to handle multiple different keyboards, for example both for latin text as well as
// numeric keyboard.
// But I agree that also enabling the keyboard to declare in the manifest which types it supports
// is a good idea.
interface <strike>InputMethodConnection</strike> InputContext: EventTarget {
// The tag name of input field, which is enum of "input", "textarea", or "contenteditable"
