You can do it in the desktop app as well. If you run it with SLACK_DEVELOPER_MENU=true in env vars, it'll enable you to right click to Inspect Element, open devtools and run this code snippet there
Disable new Slack WYSIWYG editor with this bookmarklet
31–40 of 110 posts
Re: Disable new Slack WYSIWYG editor with this bookmarklet
#32Doing some security debugging on Slack desktop a year or so ago, I saw that you could easily open up a Chrome debugger port via CLI option to use with puppeteer/chromedp/etc. I haven't checked lately, but in theory it should be easy enough to connect to the debug port and run this short script to get the same benefit in the Electron app.
You should be able to press Cmd+Shift+I and open the developer console.
Re: Disable new Slack WYSIWYG editor with this bookmarklet
#33Re: Disable new Slack WYSIWYG editor with this bookmarklet
#34 Hi there, when the WYSIWYG editor rolled out, I was pleased to see it could be disabled with the "Aa" button in the bottom right. I quickly realized it's not disabled, the toolbar is just hidden.
Here are the problems I run into:
1. Typing ``` and then pasting and typing it again (force of habit from *every other service that uses Markdown* including Slack up until this point), leaving me with an extra ``` inside my code block.
2. Typing >, pasting, and hitting enter too quickly that it doesn't seem to register. Or it registers for one line, but not the rest. Then I have to fix the rest. I'd prefer the old method of simply typing > in front of each line, consistently. But even when I try this, sometimes > doesn't get converted to quotes.
3. Typing :emoji_name: often times results in me typing the name too quickly, and, similar to the bad auto-selection of @-names, it chooses an emoji whose name I didn't type (even though I typed an emoji name exactly). Please just don't touch it until the full thing is parsed on send.
4. *foo*, _foo_, etc. -- again, I type very quickly (~158wpm when going my fastest) and these aren't getting converted. I'd expect if they don't get converted when I type it, they'd at least get converted on send. They don't.
Please give me a way to opt out of this or drastically improve it. Thank you.
I was disheartened to hear that Slack is adamant they will not allow this to be disabled: 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 feedback on board, disabling the new formatting tool isn't an option that we will be offering.
We are committed to doing what we can to improve the new experience for you, and will continue to make improvements to the new editor. Thank you for sharing these specific examples as we're carefully reviewing all feedback and passing it over to our product team.Re: Disable new Slack WYSIWYG editor with this bookmarklet
#35I personally don't mind the new WYSIWYG. Doesn't get in the way much at all really. The only thing it's weird with I find is the code blocks, (previously 3 backticks, linebreak, code, linebreak, 3 backticks). Not a massive fan of how after 3 backticks it now puts an inline code format 'block', seems a bit weird.
The three backticks is what got me, I tend to paste blocks in and then put backticks around them, which is just broken now as it just inlines the first line and does nothing to the last line, I'll just disable it for now and set a reminder for sometime soon to see if they've fixed it
Re: Disable new Slack WYSIWYG editor with this bookmarklet
#36Earlier quoted context omitted.
I wonder if the people who complain about Electron apps will refrain from doing this out of principle.
well, they can use the browser version and have this snippet working without any extra steps
Re: Disable new Slack WYSIWYG editor with this bookmarklet
#37I've been struggling with the new editor for the past week or so. I finally sent this feedback to Slack today: Hi there, when the WYSIWYG editor rolled out, I was pleased to see it could be disabled with the "Aa" button in the bottom right. I quickly realized it's not disabled, the toolbar is just hidden. Here are the problems I run into: 1. Typing ``` and then pasting and typing it again (force of habit from *every…
It's not a "workflow" app, it's a chat app.
Re: Disable new Slack WYSIWYG editor with this bookmarklet
#38You can do it in the desktop app as well. If you run it with SLACK_DEVELOPER_MENU=true in env vars, it'll enable you to right click to Inspect Element, open devtools and run this code snippet there
Only regular menu appears on right-click.
Re: Disable new Slack WYSIWYG editor with this bookmarklet
#39Earlier quoted context omitted.
well, they can use the browser version and have this snippet working without any extra steps
I don't understand the point of electron for applications whose functionality is entirely dependent on being online anyway. At that point, just use a browser as it's one fewer item to install. Is the Electron version of Slack capable of anything beyond the browser version?
Re: Disable new Slack WYSIWYG editor with this bookmarklet
#40Earlier quoted context omitted.
well, they can use the browser version and have this snippet working without any extra steps
I don't understand the point of electron for applications whose functionality is entirely dependent on being online anyway. At that point, just use a browser as it's one fewer item to install. Is the Electron version of Slack capable of anything beyond the browser version?