- From: Grisha Lyukshin <Grisha.Lyukshin@microsoft.com>
- Date: Thu, 25 Jul 2019 20:31:12 +0000
- To: Johannes Wilm <johannes@fiduswriter.org>
- 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>
- Message-ID: <DM5PR00MB04228A9CB0C2A17A981B51B6FEC10@DM5PR00MB0422.namprd00.prod.outlook.com>
Hi Johannes, Creating issues on the explainer repo is probably best in terms of tracking the issues where the document is. Yes, we do intend to discuss this at TPAC. Sent from Outlook<http://aka.ms/weboutlook> ________________________________ 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%7CGrisha.Lyukshin%40microsoft.com%7C8b4ed31beec5424ed74508d7107b9d76%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995439291891&sdata=o6uBIVugpvEjgwI8mt0VEwsY6ZOYjFNUiKNW7w02wtI%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%7CGrisha.Lyukshin%40microsoft.com%7C8b4ed31beec5424ed74508d7107b9d76%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995439301889&sdata=3X4su9wT4MvLI1bc7uuMQW%2BKIsOy87AZNKKf%2B2Dohuc%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<mailto: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%7CGrisha.Lyukshin%40microsoft.com%7C8b4ed31beec5424ed74508d7107b9d76%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995439301889&sdata=keMRUnRoMTlk8hyl2Q3lxAj4tU2t1qhXTeJ7oGB0iH8%3D&reserved=0> [http://discourse.wicg.io/uploads/default/original/2X/a/a288a739a232c851093e1609f65b40a05b3ed913.png]<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdiscourse.wicg.io%2Ft%2Fproposal-editcontext-api%2F3656&data=02%7C01%7CGrisha.Lyukshin%40microsoft.com%7C8b4ed31beec5424ed74508d7107b9d76%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995439311882&sdata=rphMlrOtkOs1Hjdc8nmxWjQffv7UpqUDe0h8gKzJiqg%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%7CGrisha.Lyukshin%40microsoft.com%7C8b4ed31beec5424ed74508d7107b9d76%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995439311882&sdata=rphMlrOtkOs1Hjdc8nmxWjQffv7UpqUDe0h8gKzJiqg%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%7CGrisha.Lyukshin%40microsoft.com%7C8b4ed31beec5424ed74508d7107b9d76%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995439321877&sdata=VQhEHXMxfEvWx4%2Fv9TdlZUKN5D7y%2FCQpOcicfFUJDv4%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%7CGrisha.Lyukshin%40microsoft.com%7C8b4ed31beec5424ed74508d7107b9d76%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995439321877&sdata=Vci5JYtTPEQ%2Bga%2BAw%2BxztuE6KmS5u1tADsHcJ2iwepI%3D&reserved=0> [http://discourse.wicg.io/uploads/default/original/2X/a/a288a739a232c851093e1609f65b40a05b3ed913.png]<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdiscourse.wicg.io%2Ft%2Fproposal-highlight-api%2F3679%2F3&data=02%7C01%7CGrisha.Lyukshin%40microsoft.com%7C8b4ed31beec5424ed74508d7107b9d76%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995439321877&sdata=Vci5JYtTPEQ%2Bga%2BAw%2BxztuE6KmS5u1tADsHcJ2iwepI%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%7CGrisha.Lyukshin%40microsoft.com%7C8b4ed31beec5424ed74508d7107b9d76%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995439331868&sdata=ZL%2FjctWdYq21xARWf%2BWOZzxR0SIVwcR4TXeA8LnzHh4%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%7CGrisha.Lyukshin%40microsoft.com%7C8b4ed31beec5424ed74508d7107b9d76%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995439331868&sdata=fq1x988i5GItkLaCOX1kq7TiMqXPRHdDHAMGcVx%2Bfk8%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%7CGrisha.Lyukshin%40microsoft.com%7C8b4ed31beec5424ed74508d7107b9d76%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995995439341864&sdata=f1%2BmXyCZ5wumsg1DV%2FhCRly352jqrYhbc%2Fxd5ge5B40%3D&reserved=0>
Received on Thursday, 25 July 2019 20:31:38 UTC