Disable new Slack WYSIWYG editor with this bookmarklet

[d4rky]

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

[ihuman]

Alternatively, you can run `launchctl setenv SLACK_DEVELOPER_MENU true` and then the dev menu will work if you launch slack from anywhere, and will persist until you log out.

If you create the following plist in ~/Library/LaunchAgents, macOS will set that env variable every time you log in (except if you tell it to reopen windows when logging back in). Change "NAME.OF.FILE" to the plist's filename without the .plist extension.

  <?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
  <plist version="1.0">
  <dict>
   <key>Label</key>
   <string>NAME.OF.FILE</string>
   <key>RunAtLoad</key>
   <true/>
   <key>ProgramArguments</key>
   <array>
    <string>sh</string>
    <string>-c</string>
    <string>launchctl setenv SLACK_DEVELOPER_MENU true</string>
   </array>
  </dict>
  </plist>

[underwater]

I wonder if the people who complain about Electron apps will refrain from doing this out of principle.

[pavel_lishin]

This is incredible.

[CraneWorm]

I set the env variable but I can't seem to get the access to devtools?

Only regular menu appears on right-click.

[johnmaguire2013]

I'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 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.

[ryeights]

For mobile users:

>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.

[strictnein]

Really frustrating seeing them repeat the "disrupting your workflow" bit.

It's not a "workflow" app, it's a chat app.

[t34543]

Slack is extremely hostile towards user feedback. I sent them comments on what I believe to be a terrible feature and they also told me it will never be changed.

[tradesmanhelix]

Maybe if they start getting enough emails/tweets they will reconsider this...emailing them now...

[metalliqaz]

I don't use slack so the issue isn't on my radar, but if this has made it to the top of HN.... I guess Slack reeeealy effed up.

[jrockway]

I think it's the product of popularity and the impact of the bug. Slack is exceedingly popular, so any change is going to come under a lot of scrutiny.

It is not clear to me how many new features Slack needs. Clearly people were able to successfully use the old text-entry UI; there was no shortage of Slack messages.

I feel like it would be better for them to focus on things that will add value to their platform without affecting people that are already using the core product. Meeting scheduling, corporate directory, video conferencing... nobody is in a better position to do that than them. And you can add those things, charge extra money for them, and not upset your existing customers.

Sometimes software is "done". The core of Slack is done.

[brootstrap]

hilariously and non-ironically i complained about this to my co-workers today. I was like yo did slack change their shit or am i going crazy? Now i'm on here seeing 800 comments and i'm laughing my butt off at how upset people are.

i get it, i typed a couple snippets already with backticks and it did weird stuff. took 5 minutes and guess what dont care

[cycrutchfield]

It’s a tempest in a teapot. Yes, the new editor is horrible. But at best it is a minor annoyance, and most users learn to work around it.

[tedivm]

I think where they really messed up is how they've been responding to people about it. They're literally telling people that they'll listen to feedback but also that they won't change anything, all in the same response. The way they treat their customers is really going to hurt them in the long run, especially as other solutions come out (Microsoft Teams already has significantly more monthly users than Slack does).

[self_awareness]

There are browser plugins like Greasemonkey or Tampermonkey that manage these kind of patches.

I'm often removing some "functionality" of a website I visit often (e.g. removing annoying chat boxes)

There are also repositories of scripts like GreasyFork (https://greasyfork.org). I suggest that maybe your script could be ported to Tampermonkey instead of distributing it as a bookmarklet.

[benbristow]

I 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.

[faceplanted]

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

[aembleton]

Seems weird, but I'll get used to it

[parliament32]

Good news, they're backpedaling. Just got this in a support request:

>We really appreciate your feedback, and we hear your frustration. We're sorry for the impact this is having on your ability to communicate with your team and on your overall productivity. We made a mistake by forcing everyone into this feature without providing an opt-out for customers like you: people for whom the existing behavior was working just fine.

>We've started working on a preference that will let you return to the previous message composer. We don't have a specific release date to share right now — it's this team's top and only priority, however, and we expect to have it available on the desktop within a couple of weeks, with Android following shortly thereafter.

>We will follow up with another note when this option is available to you, and we'll include instructions on how to enable it.

>Again, we're sorry for the disruption and we're grateful for the feedback. We missed the mark on this feature! We will do our best to learn from this and avoid similar mistakes in the future.

[lordfoom]

> we expect to have it available on the desktop within a couple of weeks,

A couple of WEEKS???

[perlgeek]

Wouldn't this make more sense as a tampermonkey / greasemonkey userscript?

That way it loads automatically when you visit slack, no need to repeat anything.

Disadvantage would be that you need a browser extension.

[TeMPOraL]

Shouldn't be hard to copy-paste the provided code into Tampermonkey.

[jeffchien]

Could be that some organizations disable browsers addons/extensions on their workers' browsers. Still, the option would be nice.

[ed_blackburn]

I'm not going to do this on every refresh. I predict the market/ecossytem for guerrilla browser extensions targeting technical Slack users hotting up.

[semiotagonal]

How hard would it be to run Slack in a special VM that brokered UI events from another application?

I.e. the latest Slack would be running in a VM that made everything seem normal to it, but in reality the UI input and output would be supplied by another application which was presenting a "Slack Classic" interface to the actual user.

[heharkon]

Isn't it the old functionality with the "Aa" toggle button? At least I don't have any problems with that after pressing it.

[gknoy]

Fenced blocks and `monospaced` stuff still behave frustratingly whether I have the "Aa" button toggled or not. I hate it -- wish they'd just add support for plain markdown as an option :(

[kodablah]

Doing 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.

[tolqen]

You should be able to press Cmd+Shift+I and open the developer console.

[aashcan]

Just got another note from them:

  We really appreciate your feedback, and we hear your frustration. 
  We're sorry for the impact this is having on your ability to communicate with your team and on your overall productivity. 
  We made a mistake by forcing everyone into this feature without providing an opt-out for customers like you: people for whom the existing behavior was working just fine.

  We've started working on a preference that will let you return to the previous message composer. 
  We don't have a specific release date to share right now — it's this team's top and only priority, however, and we expect to have it available on the desktop within a couple of weeks, with Android following shortly thereafter.

  We will follow up with another note when this option is available to you, and we'll include instructions on how to enable it.

  Again, we're sorry for the disruption and we're grateful for the feedback. 
  We missed the mark on this feature! We will do our best to learn from this and avoid similar mistakes in the future.

[mangatmodi]

Thank you. It was kind of Broken. I copy pasted a text with code tags and it didn't recognized. Quite painful overall.

[jaywalk]

I'd imagine that once this "experiment" is rolled out to 100% of the user base and no longer an "experiment" they will remove the feature flag and the code for the old input box.

[anaphor]

This isn't working for me on Firefox 68 (I have a newer version on my other laptop I'll try out later).

I get CSP errors: `Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”).`

I doubt it's something that can be fixed without writing a plugin / user script.

Kudos for figuring out how to disable it though!

[p0cc]

I made a firefox/chrome extension based on this script.

  * Firefox Addon: https://addons.mozilla.org/en-US/firefox/addon/disable-slack-wysiwyg/
  * Chrome Extn: Pending Review
  * Source: https://github.com/pocc/no-wysiwyg

edit: formatting

[stefan_]

I guess the fact that this is some absurd string-based-programming code is bonus entertainment. '[19] Bulk add experiment assignments to redux'!

[machiste77]

This is the content I come here for. True hacker news.

[ipoopatwork]

Don't forget to complain using /feedback !

[Justsignedup]

I for one love it.

That is all.