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

This is genius #3

Open
nicola opened this issue Mar 15, 2016 · 4 comments
Open

This is genius #3

nicola opened this issue Mar 15, 2016 · 4 comments

Comments

@nicola
Copy link

nicola commented Mar 15, 2016

This is incredible work, having such small and concise semantic for something so difficult.
Thanks for the great work. (Documentation on this particular module is needed, it is very powerful)

Ciao

@marcelklehr
Copy link
Member

Thanks for the feedback! :) I'm going to add some examples as well as an explanation of how it works.

@johanneswilm
Copy link

Is this working 100%of the time without any issues? Or is this mostly a research project?

@marcelklehr
Copy link
Member

Hey @johanneswilm! (We met before in diffDOM's isues, I believe :))
I'd like to say it's working 100% of the time, but you know how it is... Check out http://beta.hivejs.org/documents/2 to see a demo (about 60% availability, atm ;))

@johanneswilm
Copy link

Hey, @marcelklehr, Yes, indeed, we did! Great to see this come along. I see you are using CKeditor, etc. on top of it, and that seems sensible to me. As you probably have found out, every few months there is someone who tries to launch a micro-library to run with contenteditable and that usually works well for a simple demo, but badly for real content work. It's also dangerous, because many of these projects are able to attract decision makers in organizations who don't understand why this is all so complex.
We switched away from using diffDOM to prosemirror a few months ago, mainly because it took so extremely many resources to try to maintain our own editor code on top of contenteditable in a way that would work across all browsers. In future versions of the popular large editing engines, it is my understanding that they all are moving toward using a model that holds the document contents and the contenteditable just being used to get input from the user.
diffDOM has taken on a life of its own though and is being used by various other projects.
Should you come across major issues with the contenteditable, let me tell you that in the W3C editing taskforce we are trying to create a new and simpler interface where the JavaScript will get to decide most things, and we like to hear from projects such as this on what issues they currently have in that regard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants