里克文本编辑：非技术客户的高级选项
多年来，我们一直在为客户使用哪种富文本编辑器而苦苦挣扎。我们的大部分客户请求都与编辑器有关，我们总结了 90% 的原因是以下原因的组合：
- 客户不理解任何 HTML，只能使用编辑器提供的内容。
- 客户想要做“高级的东西”，比如照片下专门格式化的页脚（我们为此类请求创建类），并结合浮动框和特殊字体。
- 客户从其他地方复制东西——尤其是Word。
- 图片也出现在文章中。
从客户的角度来看，这些并不是过于疯狂的事情，我希望能够真正支持这一点。然而，经过这么多年并尝试了几种编辑器（主要是 CKEditor 和 TinyMCE），我们总是因为出现问题而不断收到请求。我们通常会手动修复它或在编辑器中修改内容，但我真的很感兴趣这是否正常。是否有富文本编辑器可以轻松完成上述操作并且不会造成太多麻烦？您的客户是否也有这些问题？
We've for years been struggling on what Rich Text Editor to use for our clients. The large share of our client request concern issues with the editor, and we have summarized the causes to be 90% of the time a combination of the following:
- Client does not understand anything of HTML and can only use what the editor provides.
- Client wants to do "advanced stuff" like specifically formatted footers under photos (we create classes for these kinds of requests), combined with floating boxes and special fonts.
- Client copies stuff from other places - especially Word.
- Images go into the article as well.
From a client-perspective, these are not overly crazy things, and I want to be able to actually support this. However, after so many years and trying several editors (mainly CKEditor and TinyMCE) we always end up with continuous requests because things go wrong. We generally fix it manually or hack up things in the editor, but I am really interested if this is normal. Are there Rich Text Editors that can do the above easily and without causing much trouble? Do your clients also have problems with these things?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
网络上的富文本编辑是一个复杂的问题。实际上，销售 ckeditor 和tinyMCE 等产品的供应商受到浏览器提供的富文本编辑引擎功能的限制。
每个编辑器只是一个 iframe 文档，其中 contentEditable 设置为 true。这公开了浏览器的底层 RTE 引擎，包括该浏览器的所有怪癖和实现细节。
最重要的是，在浏览器的当前状态下，您永远无法在浏览器中实现类似的体验。时期。您的客户总是对网络上的富文本编辑抱有不切实际的期望。
我们的工作是通过管理期望来缓解问题。他们需要知道这是网络，而不是 Word。他们需要知道大多数事情都会顺利进行，但有些事情会很糟糕。他们还需要知道，所有浏览器之间的情况永远不会保持一致。
Rich text editing on the web is a complex problem. Effectively, vendors that sell products like ckeditor and tinyMCE are restricted by what the browsers provide in terms of a rich text editing engine.
Each editor is merely an iframed document with contentEditable set to true. This exposes the underlying RTE engine of the browser, including all the quirks and implementation specifics of that browser.
Bottom line is, you are never going to achieve a word like experience in the browser with the current state of browsers. Period. Your clients will always have an unrealistic expectation of rich text editing on the web.
Our job is to mitigate the problems through managing expectations. They need to know that this is the web, not Word. They need to know that most things will work OK, and some will work poorly. They also need to know that things are never going to be consistent across all browsers.