Live data from Hacker News

Disable new Slack WYSIWYG editor with this bookmarklet

github.com

61–70 of 110 posts

Re: Disable new Slack WYSIWYG editor with this bookmarklet

#61
post #51
post #34

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…

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.

This is what "opinionated" looks like.

Re: Disable new Slack WYSIWYG editor with this bookmarklet

#62
post #34

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…

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 e…

>For mobile users:

Damn near impossible to read on my 4k desktop monitor too. Is there a reason people are so insistent on using the monospace formatting for quotes?

Re: Disable new Slack WYSIWYG editor with this bookmarklet

#63
post #62

Earlier quoted context omitted.

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 e…

>For mobile users: Damn near impossible to read on my 4k desktop monitor too. Is there a reason people are so insistent on using the monospace formatting for quotes?

I tried using a quote first, but the fact that you need to double-space between paragraphs, even when using the > symbol broke the formatting.

To avoid spending too much time figuring it out, I switched to blockquote. Sorry!

Re: Disable new Slack WYSIWYG editor with this bookmarklet

#65
post #36

Earlier quoted context omitted.

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?

You can include native code in Electron apps. I am not sure it is actually needed in any of the messaging Electron apps (Slack, Discord), but the capability is there. My favorite Electron app is Balena Etcher. It is "dd" but uses 200MB of RAM. It is AMAZING.

Does it actually include any native code, or does it just wrap `dd`?

I tried this app and it was beyond awful. I went back to `dd`.

Re: Disable new Slack WYSIWYG editor with this bookmarklet

#66
post #61
post #51

Earlier quoted context omitted.

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.

This is what "opinionated" looks like.

Something something Steve Jobs

Re: Disable new Slack WYSIWYG editor with this bookmarklet

#67

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.

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.

Re: Disable new Slack WYSIWYG editor with this bookmarklet

#68
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!

Re: Disable new Slack WYSIWYG editor with this bookmarklet

#69
post #39

Earlier quoted context omitted.

Some users prefer having a separate app with its own icon and window instead of another tab in a browser. It keeps things Separate

You can just create a shortcut with a custom icon that opens slack in a new browser window then.

Missing the point. I don't want it in my browser. My browser is used for reference materials and things like that. My chat app is its own separate thing and easily switched to.

Re: Disable new Slack WYSIWYG editor with this bookmarklet

#70
post #7
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 :(

Do you still have issues with monospaced and fenced blocks if you refresh Slack?

I tested and it was very buggy when I read the other HN thread this morning (I'm in Europe), but as of right now I can't reproduce the issues.

Post reply on HN