Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EditContext #199

Open
BoCupp-Microsoft opened this issue Aug 30, 2019 · 10 comments
Open

EditContext #199

BoCupp-Microsoft opened this issue Aug 30, 2019 · 10 comments
Labels
venue: W3C Specifications in W3C Working Groups

Comments

@BoCupp-Microsoft
Copy link

BoCupp-Microsoft commented Aug 30, 2019

Request for Mozilla Position on an Emerging Web Specification

Other information

This is an API to enable the text input services of the OS (IME support, emoji picking, handwriting recognition panel, etc) without needing an editable element in the DOM to be focused. Without something like this API, sites like Word Online, Google Docs and the Monaco editor need to scrape their input out of an editable element - the code is complex and has a negative impact on accessibility. We are working with them on this proposal and they have expressed interest in it. Please see the explainer for details.

Thanks in advance for your thoughts!

@masayuki-nakano
Copy link

Sorry for the delay to reply. I'm still reading the proposal and thinking concerns of it when I have much time.

@dbaron dbaron added the venue: W3C CG Specifications in W3C Community Groups (e.g., WICG, Privacy CG) label Nov 16, 2019
@marcoscaceres marcoscaceres removed the venue: W3C CG Specifications in W3C Community Groups (e.g., WICG, Privacy CG) label Dec 10, 2019
@marcoscaceres
Copy link
Contributor

Removed WICG label, as this is not yet a WICG adopted spec.

@dbaron dbaron added the venue: W3C Specifications in W3C Working Groups label May 22, 2020
@smaug----
Copy link
Collaborator

This was discussed during TPAC
https://lists.w3.org/Archives/Public/public-editing-tf/2019Oct/0004.html

The idea to have a way to deal with text input without DOM sounds good to me, but the proposal feels still rather rough idea and it hasn't been updated based on the feedback at TPAC.

@annevk
Copy link
Contributor

annevk commented May 28, 2020

My worry is that we haven't seen much progress on the interoperability issues with existing editing primitives. So to then add a new set of issues is not a particularly appealing proposition.

@BoCupp-Microsoft
Copy link
Author

@annevk We're making progress with an actual implementation and sample applications and are finding and resolving issues. We will update the documents based on our progress.

If you have specific interoperability issues with existing editing primitives beyond those we've enumerated in the explainer, please be sure to call those out so we don't miss anything you're worried about.

Thanks!
Bo

@alexkeng
Copy link

Hi we have updated spec draft and explainer for EditContext. Could you help reevaluate the feature and provide Mozilla's position? Thanks!

Here is the latest spec draft:
https://w3c.github.io/editing/docs/EditContext/index.html

her is the explainer (the API surface is little outdated compared to the spec draft, but there is more introductory info):
https://github.com/alexkeng/editing/blob/gh-pages/docs/EditContext/explainer.md

@annevk
Copy link
Contributor

annevk commented Feb 11, 2022

To give an update here, evaluation is on hold pending an update to the specification. w3c/edit-context#23 is the most significant issue we've raised I think, but there are a couple of others too.

@dandclark
Copy link

We've made a number of changes that address the feedback raised in w3c/edit-context#23 and the sub-issues linked from there. Individual changes can be seen at https://github.com/w3c/edit-context/commits/gh-pages but some of these are broad-sweeping and overlapping so it's probably simplest to just take another pass through the spec.

The spec has also moved since this Issue was last active: the new link is https://w3c.github.io/edit-context/

Mozilla reviewers, could you please take another look?

@masayuki-nakano
Copy link

Thank you. I'm starting to check the latest draft.

@marijnh
Copy link

marijnh commented Aug 22, 2024

This issue has been quiet for a while now. I see there is now an issue on the Mozilla bug tracker labeled "Implement EditContext", but that was opened by a person with a microsoft.com email address, so I'm not sure whether it implies any intention on the part of Mozilla.

As someone maintaining several editor libraries (CodeMirror, ProseMirror) that would benefit a lot from wide EditContext support, I'm still hoping this thing will at some point see adoption beyond Chromium. Is anybody at Mozilla still looking into this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
venue: W3C Specifications in W3C Working Groups
Projects
Status: Unscreened
Development

No branches or pull requests

9 participants