inputPanelPolicy as a way to control software keyboard

It has been brought up by few online editors that they need a way to control a software keyboard by not making it to show up in certain cases. Detailed discussion can be found here.

EditContext API proposal exposes such an attribute and we think, it would be beneficial to expose it on all editable elements.

The idea is to introduce an inputPanelPolicy attribute that when set to manual will prevent software keyboard from showing up even when there is user focus tap. This is a html spec related issue, but we wanted to get some feedback from the community on the proposed solution.

some early thinking:

inputPanelPolicy when set to manual before user taps on the editable field, will prevent the software keyboard from showing up.

If a web developer wants to drive software keyboard regardless of its current state, they could achieve that with also using additional inputPanelPolicy attribute values. Something like hidden and show.

So there could be a total of four attribute values: [auto, manual, show, hidden] to controls behavior of and also to drive the keyboard to appear or get dismissed.

[EDIT] I've removed reference to inputMode as it is really about controlling the layout of the virtual keyboard.

No repository file or test is named. Start by reading the linked WHATWG discussion and EditContext explainer, then determine whether inputPanelPolicy and the proposed values should be adopted. Done means the community has reached a clear decision and the corresponding HTML specification work is defined.