Re: New API proposals from Editing TFs discussions

Hey Travis,
I think there is some misunderstanding in concerns of the Editing
Taskforce. There has been a rechartering which has created the Web Apps
Working group, which is now responsible for text editing in general. Just
about all the specs we were working on are in this new Working Group so
that's where we'll continue to work on those things. A "taskforce" is
apparently just an adhoc thing that the WG can setup, so that can also be
done in the Web Apps Working Group if it is concluded that it makes sense
to have meetings concerning all the editing specs separate from the other
specs. In case a taskforce is not established, that just means that the
meetings on these editing specs will happen in the name of the entire WG
and my guess is that some people will just sit there and get very bored
because they don't really care about editing, or they will just stay way.
At any rate - there is no gap to fill by a CG for the existing spec drafts.

The one question I am still investigating is what to do with proposals for
new specs. I think these should be discussed with the same group of people
that also discuss contenteditable and input events, because a lot of this
is either an alternative or closely tied complimentary stuff and if we
decide to go for this, then there is probably less reason to for example
try to get to agreement on Input Events level 2 (or 3). And also it would
not be very productive if two browser engines decide to go for one solution
and two other engines go for the other solution just because they have been
participating in two different series of meetings and therefore reached
different conclusions on what the overall consensus is. So I think that
either all these things should continue to be discussed in the Editing
taskforce, or if W3C processes don't allow that, then the meeting at TPAC
should on paper be a joined Editing Taskforce + new CG meeting so that we
can talk about all the different proposals with the same people in the same
meeting.

On Wed, Jul 24, 2019 at 11:21 PM Travis Leithead <
travis.leithead@microsoft.com> wrote:

> I think we'd like to either jump into the WICG and incubate these
> proposals, or spin-up a new Community Group to replace the gap that the
> Editing Task Force left. If you would like to support a creation of a CG,
> we'd love it!
>
> (Note: we're aware of the HTML Editing API CG
> <https://www.w3.org/community/editing/>, but that group seemed a bit out
> of date (as noted by Alex Russell's photo 😉) and not quite geared at
> where we want to go as a group.)
>
> Definately love to have face-time at TPAC!
> ------------------------------
> *From:* Johannes Wilm <johannes@fiduswriter.org>
> *Sent:* Wednesday, July 24, 2019 2:12 PM
> *To:* Grisha Lyukshin <Grisha.Lyukshin@microsoft.com>
> *Cc:* Alessandro Curzi <Alessandro.Curzi@microsoft.com>; Bogdan Brinza <
> Bogdan.Brinza@microsoft.com>; Bo Cupp <pcupp@microsoft.com>; Anupam
> Snigdha <snianu@microsoft.com>; Sanket Joshi (EDGE) <sajos@microsoft.com>;
> Peng Lyu <penlv@microsoft.com>; Frankie Wu <frankiew@microsoft.com>;
> public-editing-tf@w3.org <public-editing-tf@w3.org>
> *Subject:* Re: New API proposals from Editing TFs discussions
>
> Hey Grisha,
> this all looks very interesting. Where would you like the discussion about
> these proposals to take place? Should one file issues on
> https://github.com/MicrosoftEdge/MSEdgeExplainers/issues
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftEdge%2FMSEdgeExplainers%2Fissues&data=02%7C01%7Ctravis.leithead%40microsoft.com%7C7adb5b805d014f8cc18508d7107bb630%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995832054733&sdata=hdIzlE3Wz4BUDo42HMRB1k7%2Bl7ShB7nC5fRIzj%2FB9Kk%3D&reserved=0> and
> add a specific label to them, should one respond to the entries on wicg.io
> <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwicg.io&data=02%7C01%7Ctravis.leithead%40microsoft.com%7C7adb5b805d014f8cc18508d7107bb630%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995832054733&sdata=LKTM60N5QfePYw9SwiSJlsX4YAow%2B5Jzgq9q9JZZUpQ%3D&reserved=0>
> or what is the preferred way?
>
> And I guess you guys would want to have a face to face discussion  as part
> of an editing meeting at TPAC as well?
>
> On Sat, Jul 6, 2019 at 1:12 AM Grisha Lyukshin <
> Grisha.Lyukshin@microsoft.com> wrote:
>
> adding few folks from Microsoft that previously expressed interest in
> these APIs.
>
> Hi Everyone,
>
> I am writing to let you know that we have couple of proposals publicized
> on WICG that were inspired by some of the discussions in Editing group.
>
> https://discourse.wicg.io/t/proposal-editcontext-api/3656
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdiscourse.wicg.io%2Ft%2Fproposal-editcontext-api%2F3656&data=02%7C01%7Ctravis.leithead%40microsoft.com%7C7adb5b805d014f8cc18508d7107bb630%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995832064732&sdata=u8jiS%2BSS11%2BdiTiq4losgl4lMTg5XykTzS03AJ93kEE%3D&reserved=0>
>
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdiscourse.wicg.io%2Ft%2Fproposal-editcontext-api%2F3656&data=02%7C01%7Ctravis.leithead%40microsoft.com%7C7adb5b805d014f8cc18508d7107bb630%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995832064732&sdata=u8jiS%2BSS11%2BdiTiq4losgl4lMTg5XykTzS03AJ93kEE%3D&reserved=0>
> [Proposal] EditContext API
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdiscourse.wicg.io%2Ft%2Fproposal-editcontext-api%2F3656&data=02%7C01%7Ctravis.leithead%40microsoft.com%7C7adb5b805d014f8cc18508d7107bb630%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995832074732&sdata=BeWX3BYfUAlLadqh9CKPaJ5ChtcvFfVbG0IVgzVSQGM%3D&reserved=0>
> EditContext API was inspired by discussions in Editing TF. It allows web
> applications a deeper integration with operating systems’ input services.
> The proposed design allows for clean separation of document object model
> and data model and a number of other benefits that are not available to a
> web developer today. Some of the gaps that the proposal aims to fill in the
> web platform: Very hard to build interoperable text editor on the web using
> browser primitives, i.e. contenteditable or textare...
> discourse.wicg.io
> <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdiscourse.wicg.io&data=02%7C01%7Ctravis.leithead%40microsoft.com%7C7adb5b805d014f8cc18508d7107bb630%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995832084723&sdata=yCNQDkd1rMA7R63RPJqKk3W5ifmEpL1%2BuXXDO3vITgk%3D&reserved=0>
> https://discourse.wicg.io/t/proposal-highlight-api/3679/3
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdiscourse.wicg.io%2Ft%2Fproposal-highlight-api%2F3679%2F3&data=02%7C01%7Ctravis.leithead%40microsoft.com%7C7adb5b805d014f8cc18508d7107bb630%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995832084723&sdata=ZrbsVdDFdmgHAUX7x3dCMy8a6fv3eP3olHOpjhlKlUI%3D&reserved=0>
>
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdiscourse.wicg.io%2Ft%2Fproposal-highlight-api%2F3679%2F3&data=02%7C01%7Ctravis.leithead%40microsoft.com%7C7adb5b805d014f8cc18508d7107bb630%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995832094726&sdata=M5UqF%2F5eUZc0iPJc0%2FmDeby7i4ykKuFgs0B2qmxXtkk%3D&reserved=0>
> [Proposal] Highlight API
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdiscourse.wicg.io%2Ft%2Fproposal-highlight-api%2F3679%2F3&data=02%7C01%7Ctravis.leithead%40microsoft.com%7C7adb5b805d014f8cc18508d7107bb630%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995832094726&sdata=M5UqF%2F5eUZc0iPJc0%2FmDeby7i4ykKuFgs0B2qmxXtkk%3D&reserved=0>
> This proposal was inspired by this issue in Editing discussions. Highlight
> API allows web developers to style arbitrary range objects without causing
> DOM updates of the view. There are a number of scenarios where this would
> be useful, including third party spellcheck and grammar extensions,
> javascript implementation of find-on-page, or javascript, rendering of its
> own selection. Currently, browsers do not provide this functionality which
> forces web developers to modify DOM in order to achieve...
> discourse.wicg.io
> <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdiscourse.wicg.io&data=02%7C01%7Ctravis.leithead%40microsoft.com%7C7adb5b805d014f8cc18508d7107bb630%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995832104717&sdata=bwZErTrcWRBBey4Xpfru6cweo4PMiOwUuCQejKIUCnE%3D&reserved=0>
> Would love for you to take a look at it and provide some feedback on the
> idea, design, etc...
>
> -Grisha
>
> Sent from Outlook <http://aka.ms/weboutlook>
>
>
>
> --
> Johannes Wilm
> Fidus Writer
> http://www.fiduswriter.org
> <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.fiduswriter.org%2F&data=02%7C01%7Ctravis.leithead%40microsoft.com%7C7adb5b805d014f8cc18508d7107bb630%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995832114707&sdata=aoxRS1bdefh1cWpvabgu7wsVlX6bcN6rSHyKrRqCz9Q%3D&reserved=0>
>


-- 
Johannes Wilm
Fidus Writer
http://www.fiduswriter.org