Someone has supplied a fix: https://github.com/kfahy/slack-disable-wysiwyg-bookmarklet
Slack’s new WYSIWYG input box is terrible
841–850 of 1001 posts
Re: Slack’s new WYSIWYG input box is terrible
#842Did Slack ship a buggier version of this yesterday? I have it on one of my workspaces, and it's fine . I can still type `backticks` in the editor, with the exact same combinations of keystrokes I used before, it's just that they render as they will on the channel, rather than showing me the backticks (and only when I type the closing backtick. GIF here: https://i.imgur.com/o3wPWN0.gif ) Triple backtick does the same,…
Once it formats your text, you are forced to use the formatting menu to change anything. They are clearly moving towards WYSWYG-only, markup is minimally supported now to facilitate transition. Sad.
You can also toggle formatting with keyboard shortcuts.
I wonder, if they introduced a keyboard shortcut that cleared all formatting, would that be a reasonable compromise?
Re: Slack’s new WYSIWYG input box is terrible
#843Earlier quoted context omitted.
Many edge cases are different. To name one: You realize after finishing your code block that the first two lines of it actually shouldn't have been part of the code block, but should have been normal text above. Go ahead and try to make this change with the new system. Compare that to what you would have done with the old, plain-text system.
Sure enough, the rich text formatting is copied. The workaround I have for this is the Get Plain Text app. It strips all formatting from copied text (either automatically or on a keyboard shortcut). Sad it's required for this use case. But at least this works.
It wasn't required a day ago.
Slack can't seriously expect us to apply clumsy workarounds to their single most important feature (text-entry) that many of us use hundreds of times per day.
In particular since the solution is as trivial as adding an off-switch.
Re: Slack’s new WYSIWYG input box is terrible
#844This is funny because I work across the street of Slack’s office in Vancouver, Canada and two Slack engineers who I frequently chat with during our daily commute already told me they —and a handful of other employees— hate the WYSIWYG input box too, but were afraid to express their feelings because their role is irrelevant compared to the people who made the decision to ship it.
Please ask them what they think of the ‘drafts’ section. I’m so fed up of losing chats to that section.
Join the hundreds of people complaining in this twitter thread, I put my beef with it in there too.
https://twitter.com/SlackHQ/status/1135955676545585164
Re: Slack’s new WYSIWYG input box is terrible
#845I'm going to take the opposite of this argument, and for bonafides, I run the product team for a 1000+ person company. I'm going to assume that this thing was tested out the wazoo, both qualitatively and behind enough feature-flags and buckets to keep Optimizely in business for a year. So I have no doubt that this wasn't just a hunch on their part, but something that they meticulously tracked. If I'm wrong, definitel…
If they had all those metrics and that many test users, how could such obvious backtick issues exist?
Even simple dog-fooding by their own internal coding team should have revealed that issue.
If they had a test group, it was definitely a group that didn't use those features to begin with and basically didn't use them in the new UI either. Meticulously tracking the wrong sample group simply leads to reams of bad data.
Re: Slack’s new WYSIWYG input box is terrible
#846This reminds me of Atlassian's god-awful WYSIWYG editor. In both cases, I get that some users can't or don't like to use a machine grammar/markup, however simple. For some people markup is bad UX. Give them a WYSIWYG; that's fine. But don't remove the markup editor if your WYSIWYG editor is anything but a perfect one-two-one replacement for markup (and I have never seen one that satisfies that). IIRC there was a time…
Yes, was looking for this post. I rarely used the markup in the previous editor, but the new editor is so buggy I keep looking for an icon to switch to markup.
Re: Slack’s new WYSIWYG input box is terrible
#847Earlier quoted context omitted.
I'm surprised that hasn't been reverted yet. It's so fucking stupid. Where did that chat go? oh it's up in drafts? WTF? Terrible UI choice. It makes no sense.
It would be okay if the channel were duplicated in the drafts section. But moved? That definitely makes no sense.
[deleted]
Re: Slack’s new WYSIWYG input box is terrible
#848I have contacted them, and they replied me with this Lucas (Slack) Nov 20, 9:15 PM PST Hi there, Thank you for taking the time to write in and provide this feedback. I apologize for the disruption to your existing workflows. Our aim is to build an editor that works for all Slack users to better format their messages and clearly communicate in channels, regardless of their technical expertise. While we are taking all…
There's always alternative clients. Ripcord ( https://cancel.fm/ripcord/ ) is not 100% there yet, but it's definitely usable, tiny, and gets out of the way.
I couldn't figure out how to select a portion of a message and copy it. My only option was to copy the whole message. Made it a bit of a PITA. This is working better: https://github.com/kfahy/slack-disable-wysiwyg-bookmarklet
(not my code)
Re: Slack’s new WYSIWYG input box is terrible
#849In their defence (not the defence of the WYSIWYG box itself) - they quite likely have done lots of user testing that has shown clear desirability, improved value to user, improved usability, etc etc. You have to remember Slack's target persona is probably no longer the Engineer (If it ever was) - it's more likely a much less tech-savvy employee who finds WYSIWYG editors very handy to create rich text inputs. I guess…
> they quite likely have done lots of user testing that has shown clear desirability, improved value to user, improved usability I have never worked at a company that did user testing or if they did it was always done in a way or interpreted in a way to back up the designer's opinion. I don't think I've once in my entire 40 yr career seen a designer test with users, find out something was bad, and change their design…
I'm a designer and I do user testing for every feature in the app I'm working on – usually using Sketch or Framer X for cases where better prototypes are needed, and in mostly all cases the design changes because of it. It's very hard to get it right in he first try, and I can't believe I'm the exception here.
Funny thing too: because I usually do the implementation of my own designs (react-native app so not so big of a barrier), I usually discover limitations of the original design and have to tweak it to better fit the medium.
Re: Slack’s new WYSIWYG input box is terrible
#850This reminds me of Atlassian's god-awful WYSIWYG editor. In both cases, I get that some users can't or don't like to use a machine grammar/markup, however simple. For some people markup is bad UX. Give them a WYSIWYG; that's fine. But don't remove the markup editor if your WYSIWYG editor is anything but a perfect one-two-one replacement for markup (and I have never seen one that satisfies that). IIRC there was a time…
Confluence/Jira is the worst product suite I've ever had the misfortune of using, I can't fathom how it became popular or who finds it useful.