On Mon, Sep 22, 2014 at 3:46 PM, Richard Schwerdtfeger <schwer@us.ibm.com> wrote: > > So, you want to modify contenteditable to "minimum". What will that do to > existing apps. that are built on it? > > As has been mentioned before, the current (and broken) contenteditable will stay the way it is, to make sure that nothing breaks for anyone. contenteditable=minimal or some derivative thereof will come additionally. With time, when all the frameworks have switched and the usage of contenteditable is close to zero, I would imagine that browser makers would likely decide to remove the contenteditable code. As for Ben's comments -- I think the question he made was to the main general purpose editors that stand for most of the user created content on the web. CKeditor is certainly one of them. Others are TinyMCE and possibly Aloha. And then there are a number of editors created by the browser makers themselves -- everything from Gmail, Google Docs to Micrsoft's online Word processor. Ben was asking whether being able to add items to the right-click context menu would be something editor creators would like to do. The issue with this was at least in the past that one can only choose to entirely replace the context menu, or not at all. If one replaced it, the browser's spell checker was gone. If one didn't replace it, there was no way to add extra options. Has this changed at all? I see for example that CKeditor has chosen to replace the context menu, and so the spell checker is gone. Would users of CKeditor not like to have access to the spell checker? Have you received any feedback on that? And for those who currently write the specs -- what more information would you need to go ahead? -- Johannes Wilm Fidus Writer http://www.fiduswriter.org
Received on Monday, 22 September 2014 15:46:51 UTC