Disable new Slack WYSIWYG editor with this bookmarklet

#1

Post by akhaku » Thu, Nov 21, 2019, 6:45 AM UTC

Disable new Slack WYSIWYG editor with this bookmarklet
github.com

Re: Disable new Slack WYSIWYG editor with this bookmarklet

#2

Post by perlgeek » Thu, Nov 21, 2019, 7:56 AM UTC

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.

Re: Disable new Slack WYSIWYG editor with this bookmarklet

#3

Post by ed_blackburn » Thu, Nov 21, 2019, 7:56 AM UTC

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.

Re: Disable new Slack WYSIWYG editor with this bookmarklet

#4

Post by lukax » Thu, Nov 21, 2019, 8:05 AM UTC

You can just toggle the old minimal input by clicking the first/third button from the right (Aa - Hide formatting).

Re: Disable new Slack WYSIWYG editor with this bookmarklet

#5

Post by heharkon » Thu, Nov 21, 2019, 8:05 AM UTC

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

Re: Disable new Slack WYSIWYG editor with this bookmarklet

#6

Post by randunel » Thu, Nov 21, 2019, 8:08 AM UTC

lukax wrote: post #4

You can just toggle the old minimal input by clicking the first/third button from the right (Aa - Hide formatting).

The toggle only hides the UI, bad behaviour stays the same.

Re: Disable new Slack WYSIWYG editor with this bookmarklet

#7

Post by gknoy » Thu, Nov 21, 2019, 8:13 AM UTC

heharkon wrote: post #5

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

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 :(

Re: Disable new Slack WYSIWYG editor with this bookmarklet

#8

Post by heharkon » Thu, Nov 21, 2019, 8:14 AM UTC

gknoy wrote: post #7

heharkon wrote: post #5

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

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 :(

Ah, true. I rarely use any markdown so I didn't notice any difference :)

Re: Disable new Slack WYSIWYG editor with this bookmarklet

#9

Post by benbristow » Thu, Nov 21, 2019, 8:21 AM UTC

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.

Re: Disable new Slack WYSIWYG editor with this bookmarklet

#10

Post by semiotagonal » Thu, Nov 21, 2019, 8:21 AM UTC

ed_blackburn wrote: post #3

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.

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.