call, 2017-07-11

present: chaals, johannes, grisha


As neither Chrome nor Webkit was present and most of the points on the
agenda are directly aimed at them, we decided to keep the agenda for the
August meeting and instead run a question-and-answer session about Grisha's
proposal of image input  in contenteditable and the overall process of how
input events can move forward within the W3c process. For that reason we
also skipped havign full minutes.


On Image input:

It would be similar to emoji input, but instead of a unicode character, it
would be an actual image. The image would come from the OS/user agent and
be served as an inline image. The advantage over emojis would be that they
would have colors and look the same on all OSes, and they wouldn't be
restricted by emoji definitions. The concept is already used as of today in
the form of "stickers" that several web apps allow.

Grisha proposes to standardize these if there is interest on the part of
editors/browsers. Johannes said he will try to find out if some editors are
interested.

On Input events:

To move toward a proposed recommendation, two or more independent
implementations are important [1], for which reason it will most likely be
Level 1 of the Input EVents spec that will move forward first (as both
Webkit and Blink conform to it). Feedback from a numebr of groups needs to
be gathered, and we are currently waiting for the two remaining groups:
Security and I18N. Both groups have been contacted in the past and chaals
will contact them again.

Chaals also wondered if any of the things we are working on are impacting
the HTML spec. He is currently gathering a list of specs for which this is
the case, adn we should contact him if we believe this is the case for any
of what we are working on.


[1] See exact requirements
https://www.w3.org/2017/Process-20170301/#implementation-experience


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