Hacker News new | ask | show | jobs
by samwillis 1569 days ago
As someone who has worked with "contenteditable" and the various javascript rich text editors, I find it quite amusing that they have made this change now. One of the hardest things to implement with contenteditable/DOM is wysiwyg page splitting. Now, just after Google abandons contenteditable/DOM for its own text editor/renderer implementation they add support to disable one of the hardest features they had to implement in the old version.
4 comments

You are right. Implementing line breaks and pagination algorithms that work well with tables and images - is one of the hardest problems in implementing a word processor. Basically, the newer gen folks want to leave the paper layouts behind and as a result the softwares are becoming simpler to architect - could be a good thing!
To be expected: Later they will post some statistic, which supposedly states, that "no one is using the old way anyway" and that it will be removed in the future.
> Now, just after Google abandons contenteditable/DOM for its own text editor/renderer implementation

Minor note, they actually made that switch 12 years ago.

https://drive.googleblog.com/2010/05/whats-different-about-n...

I dont think hardest things to implement is something Google cares of. They dont have any resources constraint