New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stopped working in newest Slack version #27
Comments
@kfahy Is this a problem with how redux dispatches? |
Ahh yeah, good find. My guess is that Slack decoupled the feature from the "wysiwyg" AB tests. The script had worked by deleting some AB tests from the client, which effectively disabled them. In the latest version of the client, even if I try to delete all the AB tests in this manner, the new editor is still enabled. |
bump |
We can disable this feature in preferences now! 🎉 |
@aasdkl yes, but no. It is still a significant degradation. For example, if you "disable" you cannot write lists like this: * One line
- Indented
* Second line It will not be parsed as markdown to create a list like it used to (prior to this awful WYSIWYG)
The output will instead look something like this:
It is bad and Slack should feel bad. |
This seems to have stopped working in the newest version of Slack. I am running the Slack Desktop app on Ubuntu 18.04.
This was working for me previously. I am constantly running Slack in "developer mode" and after each restart I have to copy-paste the content of
index.js
fromslack-disable-wysiwyg-bookmarklet
into the console in Slack. This was working as expected until very recently. I am noticing today that is no longer works to disable the WYSIWYG editor. I still have format-as-you-type functionality enabled in Slack. Additionally, I have discovered a new "feature" that is when I paste content with markdown in it:...I am seeing a little popup message that says "Apply Formatting?". If I do not apply formatting, this message doesn't get formatted at all. I was able to submit a message with Markdown and have it work as expected (that is display as formatted text in the chat history). This seems to have changed within the last few days.
The text was updated successfully, but these errors were encountered: