> I think it depends on a few factors such as the actual code complexity
As I mentioned earlier, the code is simply more complex than it needs to be at the moment. Removing what I would consider to be non-essential code from the existing rich TextArea component and related DOM classes will streamline the codebase (i.e. reduce the overall complexity) and will most likely allow us to create a more efficient solution for editing in the future, if we so choose. > Its not clear it's a high-priority area for pivot as a project. I agree that it may not be the highest priority right now. However, that doesn't make the concept any less valuable. At least one user has already requested such a feature, and I imagine that many developers might benefit from it.
