Re: Meeting agenda for TPAC

Calculating the default is based on the context of the input.

If you have an input that is of a certain type (eg type="email") it will
allow the keyboard of that type first but you could override it.

The concept is that these two fields are both applicable to input/textarea
and contenteditable.

On Tue, Oct 24, 2017 at 10:54 AM, Johannes Wilm <johanneswilm@gmail.com>
wrote:

> Ok, you have to choose one of each, each time, right? If that is the case
> then it seems like a generic/default is missing in both specs for all cases
> not covered by these options. For example, if the user enters a title in a
> field, that would not be covered by "search", nor "keyword" nor any of the
> other available options, or how is this to be understood?
>
>
> On 24 Oct 2017 4:45 pm, "Dave Tapuska" <dtapuska@chromium.org> wrote:
>
> inputmode can definitely be used for long form. Say you are entering some
> context aware area of the editable region. Modifying the inputmode on the
> content editable will adjust the current virtual keyboard.
>
> I don't expect the inputmode-action to be as useful on long form. We are
> restricted on iOS and Android of what text to put there so the range is
> also limited but for a long form you could think that a send might be
> useful if say you were building an email app.
>
> On Tue, Oct 24, 2017 at 10:39 AM, Johannes Wilm <johanneswilm@gmail.com>
> wrote:
>
>> I agree with you.
>>
>> Q: Are these also meant for long form texts/contenteditable? If so, which
>> of these actions would you typically want to display in a word processor
>> type app?
>>
>> On 24 Oct 2017 2:46 pm, "Dave Tapuska" <dtapuska@chromium.org> wrote:
>>
>>> I'd like to talk about inputmode
>>> <https://cdn.rawgit.com/dtapuska/inputmode/HEAD/index.html> and
>>> inputmode-action
>>> <https://cdn.rawgit.com/dtapuska/action-hint/HEAD/index.html>. These
>>> were blocked in the specification phase by Mozilla because they wanted to
>>> re-spec contenteditable. I don't believe what we can wait around for that
>>> to happen.
>>>
>>> dave.
>>>
>>> On Tue, Oct 24, 2017 at 6:47 AM, Léonie Watson <tink@tink.uk> wrote:
>>>
>>>> Thanks Johannes, that would be good. When the agenda is more complete,
>>>> I'll ping Ryosuke.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 24/10/2017 10:23, Johannes Wilm wrote:
>>>>
>>>>> Hey Leonie,
>>>>> I waited to see if we get clarity on whether the opinion paper posted
>>>>> by Alexandre represents the official Chromium view, as that would change
>>>>> what we need to talk about quite fundamentally.
>>>>>
>>>>> The last email makes it sound as if we are not going to get this
>>>>> clarification. So I'll put all Alexandre's proposed action items on the
>>>>> agenda but also beforeinput level 2. Then we'll see how to continue.
>>>>>
>>>>> Notice that a lot seems to be related to the selection so we should
>>>>> make sure Ryosuke is involved in this.
>>>>>
>>>>> On 24 Oct 2017 10:54 am, "Léonie Watson" <tink@tink.uk <mailto:
>>>>> tink@tink.uk>> wrote:
>>>>>
>>>>>     Johannes, Gary, & Grisha,
>>>>>
>>>>>     I need your help to put the agenda together for the Editing TF
>>>>>     meeting at TPAC [1].
>>>>>
>>>>>     We have the meeting with APA WG at 2pm, and I've added the
>>>>> Clipboard
>>>>>     API items requested by Gary at 3pm (though feel free to move it).
>>>>>
>>>>>     Can you fill in the rest of the items and/or post them to this
>>>>>     thread, and I'll add them to the agenda?
>>>>>
>>>>>     Thanks.
>>>>>
>>>>>     [1] https://github.com/w3c/WebPlatformWG/issues/93
>>>>>     <https://github.com/w3c/WebPlatformWG/issues/93>
>>>>>     --     @LeonieWatson @tink@toot.cafe tink.uk <http://tink.uk>
>>>>> carpe diem
>>>>>
>>>>>
>>>>>
>>>> --
>>>> @LeonieWatson @tink@toot.cafe tink.uk carpe diem
>>>>
>>>>
>>>
>
>