https://bugs.kde.org/show_bug.cgi?id=516111

--- Comment #3 from Nate Graham <[email protected]> ---
If the long-term intention is to always have WYSIWYG editing, then it needs to
be perfect; when WYS is not WYG, the contract is broken and the feature is not
usable.

That suggests two practical options:
1. Make the WYSIWIG feature perfect
2. Provide a way to opt out of WYSIWYG mode and use plaintext mode again

Right now unfortunately the WYSIWYG feature is fairly far from perfect. I
encounter so many basic bugs that I've had to stop using NeoChat because basic
text entry is not usable for me anymore. So I agree with making it optional for
26.04, since there's not a lot of time to make it perfect enough to use. I
would even recommend reverting it on master and developing it more in a branch
before trying again.

For what it's worth, here are the post-rich-text-chat-bar regressions that are
making NeoChat really hard for me to use now:

Bug 516116 - Impossible to enter a properly-formatted list now 
Bug 516536 - Impossible to enter a code block now
Bug 516106 - When *not* using the rich text bar, markdown-style list markup is
transformed into rich text anyway and messed up
Bug 516114 - Rich text formatting mode isn't exited when deleting formatted
text 
Bug 516260 - Replying to a message doesn't focus chat text field
Bug 516537 - The way to send a message or enter a new line unexpectedly
reverses between normal and rich text controls mode
Bug 516245 - Chat text field's clickable area is truncated
Bug 516104 - Two context menus when right-clicking on messages 
Bug 516123 - You can now open multitiple emoji popups 
Bug 516122 - Emoji button is hidden in the rich text bar now
Bug 516100 - Compact delegate style no longer vertically centers unread bubble

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to