I had no idea it was a feature. I just thought my Slack App was acting weird and needed a reboot. Oh dear.
Slack’s new WYSIWYG input box is terrible
71–80 of 1001 posts
Re: Slack’s new WYSIWYG input box is terrible
#72The specific example shown in the attached article works fine for me in Slack with the updated editor. ``` when you do `foo()` it foos the bar. ``` Looks fine for me? Only the `foo()` is highlighted, not the entire line as shown. Have they pushed out a fix for this already?
According to the Slack twitter, yes (https://twitter.com/SlackHQ/status/1192199216157868037)
Re: Slack’s new WYSIWYG input box is terrible
#73Reading their non-replies on Twitter feels like I'm reading something specifically designed to piss me off. Smarmy apologies, low empathy, cocksure of how correct their vision of a chat service should be. This one in particular[1]: > The goal is for workflows to evolve, but we realize change can be a bit of a pain. "Stupid peasant, we are only here to help you. Once you see the glorious vision we have you will thank…
Is there any way that tweet could have been written that would have satisfied you, without actually agreeing to change course right away?
To me the tweet's tone says that they honestly care and don't want people to be inconvenienced, but also want to at least see if people will warm to it.
There has to be some kind of healthy balance between listening to user feedback and never changing anything. The extreme version of listening to user feedback is: https://xkcd.com/1172/
Re: Slack’s new WYSIWYG input box is terrible
#74Since moving companies, I have traded slack for microsoft teams. Teams is pretty terrible in comparison, one of the most annoying "features" is it's WYSIWYG editor, I have no idea why slack would want to copy one of the worst elements about teams.
Because teams is eating their lunch by virtue of being included in Office 365, and they misinterpret it as being due to their WYSIWYG editor?
Re: Slack’s new WYSIWYG input box is terrible
#75YES IT IS. I literally am not able to enter some things, like a `>` quote followed by a line that is NOT a quote.
Re: Slack’s new WYSIWYG input box is terrible
#76I've given up entirely on the Slack desktop app and use Ripcord exclusively. Much faster, more responsive and easier to use for 99% of my time spent on slack.
I'm giving this a whirl now. I can't stand forced WYSIWYG and I know this minor annoyance is going to slowly grind on me over time.
Re: Slack’s new WYSIWYG input box is terrible
#77Earlier quoted context omitted.
Smells of bad UX/design process - some senior "wants" this particular solution, despite their users showing direct feedback that it doesn't work for their needs.
I'd push back on your last point; there's a zero-sum feedback process here that is invisible. You're seeing the negative feedback from a vocal set of minority power users; the positive feedback from people isn't going to be known or seen in anything other than usage metrics. You say "users": how many, what percentage, what cohort..you get the idea.
[deleted]
Re: Slack’s new WYSIWYG input box is terrible
#78> there is no way to go back to plain old Markdown input
Can’t you just tap on the “Aa” icon to hide it?
Re: Slack’s new WYSIWYG input box is terrible
#79I'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…
Don't know why you're getting down-voted, this is a logical and sensible conclusion, from a business perspective.
It's logical from a short-sighted perspective as I'm sure it looks good to investors to have a longer checklist of features. But shipping a broken feature is eroding customer trust.
Re: Slack’s new WYSIWYG input box is terrible
#80They totally messed me up. Where are my snippets?