Re: Proposed agenda for call on Tuesday

Hey,
yes, we postponed most of the points to the August call as we assumed
Google's absence was about holidays. So we're still interested in the
points about input events.

On Wed, Jul 12, 2017 at 11:32 PM, Alexandre Elias <aelias@chromium.org>
wrote:

> Sorry for not replying/attending, I just got back from vacation.  I'd be
> interested in reading the meeting minutes and may still be interested in
> attending future calls where relevant.
>
> On Mon, Jul 10, 2017 at 5:53 AM, Johannes Wilm <mail@johanneswilm.org>
> wrote:
>
>> Hey Grisha,
>>
>> ok, point has been added.
>>
>> The meeting time should be 10 AM San Francisco on Tuesday 2017-07-11.
>> This translates to 1900 Berlin/Madrid on the same day.
>>
>> I have not heard back on whether the call-in details from last time still
>> are valid. I hope we hear something about that in the next few hours.
>>
>> On Thu, Jul 6, 2017 at 6:31 PM, Grisha Lyukshin <glyuk@microsoft.com>
>> wrote:
>>
>>> Thanks, Johannes,
>>>
>>>
>>> Somehow, I lost meeting details. Could you please share it?
>>>
>>>
>>> Also, I wanted to add another item to the agenda:
>>>
>>>
>>> Need of rich content input in html controls(think of gifs insertion with
>>> a keyboard shortcut or through an IME). Is this something editors
>>> need/want? If so, how would you want it to be exposed to you? new element,
>>> new CE attribute value, etc?
>>>
>>>
>>> - Grisha
>>>
>>>
>>> Sent from Outlook <http://aka.ms/weboutlook>
>>> ------------------------------
>>> *From:* johanneswilm@gmail.com <johanneswilm@gmail.com> on behalf of
>>> Johannes Wilm <mail@johanneswilm.org>
>>> *Sent:* Wednesday, July 5, 2017 10:55:39 PM
>>> *To:* public-editing-tf@w3.org; Alexandre Elias
>>> *Subject:* Proposed agenda for call on Tuesday
>>>
>>> Hey,
>>> our monthly call is scheduled for Tuesday. Agenda items to look at so
>>> far:
>>>
>>> * Input Events, level 1:
>>> - What is the purpose of the deleteCompositionText input type? (Is there
>>> a purpose or was it left in by accident?) https://github.com/
>>> w3c/input-events/issues/66
>>>
>>> * Input Events, level 2:
>>> - Where should the normative list of the event order of an entire IME
>>> text editing operation live? (here or ui events)
>>>
>>> * Both:
>>> - How do we deal with beforeinput events for things like "intends to
>>> write subsequent text in bold" that don't yet cause a DOM change?
>>> https://github.com/w3c/input-events/issues/64
>>> - should uievents take our description of when a beforeinput event takes
>>> place, or do we need a different text? https://github.com/w3c/u
>>> ievents/issues/145
>>>
>>> Other things:
>>> - Editing text in tables, are we ok with updating spec as requested in
>>> latest tickets at https://github.com/w3c/editing/issues or should we
>>> not bother with it?
>>>
>>>
>>> Please notify the list if you have more topics to discuss. Notice that I
>>> left out the issues brought up here about getting input events 1 get closer
>>> to 2, as that debate probably will last a lot longer.
>>>
>>
>>
>>
>> --
>> Johannes Wilm
>> http://www.johanneswilm.org
>> tel: +1 (520) 399 8880 <(520)%20399-8880>
>>
>
>


-- 
Johannes Wilm
http://www.johanneswilm.org
tel: +1 (520) 399 8880