Slack’s new WYSIWYG input box is terrible (quuxplusone.github.io)

Article summary

Slack has introduced a new WYSIWYG text input feature, which has been met with criticism from users who prefer the old Markdown input method. The new feature has been found to have several issues, including problems with formatting code and inserting text at the beginning of a code span. Users are calling for the option to disable the WYSIWYG feature and revert to the old Markdown input method. Slack has since added an option to disable the WYSIWYG feature in the browser version, but it is not available on the mobile app.

Main themes

• Slack's WYSIWYG input feature
• Markdown input method
• User interface issues
• Formatting problems
• User preferences

What commenters say

• The new WYSIWYG input feature is frustrating to use and has several formatting issues.
• Some users prefer the old Markdown input method and want the option to disable the WYSIWYG feature.
• The WYSIWYG feature is not suitable for users who need to format code or insert text at specific positions.
• Ripcord, a third-party Slack client, is being considered as an alternative due to its faster response time and more customizable interface.
• The WYSIWYG feature may be more suitable for non-technical users who are familiar with Microsoft Word-like interfaces.
• The issue with the WYSIWYG feature is not just about personal preference, but also about the usability and functionality of the feature.
• Slack's decision to remove the option to configure the up arrow to repeat the last command is also seen as a regression.
• The 512x512 pixel requirement for images in the WYSIWYG feature may be related to scaling factors on high-DPI displays.