- From: Johannes Wilm <mail@johanneswilm.org>
- Date: Sun, 6 Aug 2017 08:12:05 +0200
- To: "public-editing-tf@w3.org" <public-editing-tf@w3.org>, Alexandre Elias <aelias@chromium.org>, Gary Kacmarcik (Кошмарчик) <garykac@chromium.org>, Travis Leithead <travis.leithead@microsoft.com>
- Message-ID: <CABkgm-QgfMZuE2MT2ACFNcH2-R-kUN15iqwiaOkBnsuVQSkueA@mail.gmail.com>
Hey, our monthly call is scheduled for Tuesday 10 Am San Francisco time. Proposed agenda items are below. Please email the list if you have additional items. Chrome 60 was shipped during the last month. This is important for us because Chrome 60 included with level 1 of the InputEvent spec enabled by default [1] and together with Safari 10.1 which shipped some months ago with level 2 of the InputEvent spec, we now have two independent implementations of level 1 of the Input Event spec being shipped. This is important for the W3C process and for JavaScript developers it means they can now start using the event to a higher degree (although they still need to keep alternative methods in place to target Firefox and Edge), but also for us it means that in reality we won't be able to do many changes to level 1 of the spec. Nevertheless, we need to deal with some points still to fulfill the requirements of the various review committees that have commented on the spec so far. * Input Events, level 1/2: - 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? Our current text is a bit ambiguous. https://github.com/w3c/input-events/issues/64 - Should we ask uievents take our description of when a beforeinput event takes place, should we take theirs or do we need a completely different text? https://github.com/w3c/uievents/issues/145 * Other things: - Microsoft proposal: Add a way for user agent/OS to provide "Stickers" (images) that user can insert into text editing contexts. Is there interest? - 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? [1] https://www.chromestatus.com/feature/5656380006465536 ------------------ Editing Tuesday, August 8, 2017 10:00 am | Pacific Daylight Time (San Francisco, GMT-07:00) | 1 hr Join WebEx meeting URL: https://mit.webex.com/mit/j.php?MTID=m9ceb062c225d916e92480301cbd3951f Meeting number: 641 763 871 Meeting password: [w3c] -- just the 3 characters Join from a video conferencing system or application Dial 641763871@mit.webex.com Join by phone +1-617-324-0000 US Toll Number Access code: 641 763 871 Mobile Auto Dial:+1-617-324-0000,,,641763871# Add to your calendar: https://mit.webex.com/mit/j.ph p?MTID=m24dcd2aa5d1d95e126992e531883903b ------------------ -- Johannes Wilm http://www.johanneswilm.org tel: +1 (520) 399 8880
Received on Sunday, 6 August 2017 06:12:30 UTC