HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
On the contrary, this is not difficult to implement if to replace the old Notes rendering engine with a modern browser one. This will immediately solve all text problems, and will also expand the Notes client with additional capabilities - bookmarking, etc.
I am not aiming for full round trip compatibility here as this is something that's hard to achieve (I know your products, Ben :-)) I just want some feature subset of richtext that is safe to use with major web editors AND safe to use in the client to have a common ground to work with.
While I understand the goal, the issue is a bit more complex than that. The web editors support all sorts of things. It is the conversion process that is broken, and it is broken in both directions, so round-trip editing requires fixing it in both directions.
You would be hard-pressed to find anything truly "safe" for web editing. Tables, sections, bullets, margins, fonts all have issues, so you're not much beyond a text field. The same goes for the web side, as many things you can do there don't convert back well.
Important caveat: our AppsFidelity third party product allows this round-trip editing with regular Notes rich text fields, so I am obviously biased, though it also means I know what I am talking about.