The latest version of Slack has a setting to disable the WYSIWYG editor
121–130 of 225 posts
Re: The latest version of Slack has a setting to disable the WYSIWYG editor
#122Re: The latest version of Slack has a setting to disable the WYSIWYG editor
#123Dark mode, better performances, option to disable divisive new features: Slack might be making it harder to focus at work but the product itself improved quite a lot in 2019, kudos to the PMs.
Kudos to the PMs? They allowed a half-baked (if that) feature to be shipped out and then wouldn't back down from it for a week. This reeks of PMs pushing a feature that isn't ready yet.
The rollout happened over multiple weeks, no? I know it was multiple weeks between I first saw it on any slack and it was on all of my slacks anyway.
The outcry was “ignored” (or rather, “we know what’s best” attitude) for about a week though.
Re: The latest version of Slack has a setting to disable the WYSIWYG editor
#124Earlier quoted context omitted.
Broken how? This feels like a good example of a company building and launching something, then watching and responding to how the public/users react to it. Isn't that more or less what you should do as a company? Build things and then adjust your strategy based on how the market likes or dislikes it?
Broken how? Broken in the sense that Slack kept going forward even after the complaints kept rolling in. How hard would it have been to pull the latest release?
Re: The latest version of Slack has a setting to disable the WYSIWYG editor
#125Still waiting for an option to disable "drafts" (channels all of a sudden jumping to the top of the channel list)
Your mistake is showing a channel list. Hide unread channels; it's the only way to use Slack IMO.
Re: The latest version of Slack has a setting to disable the WYSIWYG editor
#126In case anyone's interested, here's the Chromium bug(s) that's one of the main reasons the WYSIWYG editor has such issues in Chrome(/Electron): - https://bugs.chromium.org/p/chromium/issues/detail?id=102937... - https://bugs.chromium.org/p/chromium/issues/detail?id=608393 - https://bugs.chromium.org/p/chromium/issues/detail?id=608162 The gist of it is that they "canonicalize" the DOM selection when you have two adjac…
The team the size of Slack should/could have easily worked around that.
Re: The latest version of Slack has a setting to disable the WYSIWYG editor
#127Earlier quoted context omitted.
Side comment: I've tried to use Slack's dark mode but had to quit. I was constantly having to download images to be able to read the black-over-transparent background of matplotlib images (that's apparently the default for the axis, markings, legends, etc.) It's not a matter of changing my code, too, because I want to see the images posted by _other_ people
I wonder if you could add a CSS rule to set the background colour of images to white?
Re: The latest version of Slack has a setting to disable the WYSIWYG editor
#128Dark mode, better performances, option to disable divisive new features: Slack might be making it harder to focus at work but the product itself improved quite a lot in 2019, kudos to the PMs.
The other 2 amount to solving self-inflicted problems.
You are kind.
Re: The latest version of Slack has a setting to disable the WYSIWYG editor
#129In case anyone's interested, here's the Chromium bug(s) that's one of the main reasons the WYSIWYG editor has such issues in Chrome(/Electron): - https://bugs.chromium.org/p/chromium/issues/detail?id=102937... - https://bugs.chromium.org/p/chromium/issues/detail?id=608393 - https://bugs.chromium.org/p/chromium/issues/detail?id=608162 The gist of it is that they "canonicalize" the DOM selection when you have two adjac…
Not sure Chromium is to blame here. All the WYSIWYGs in all the environments I've ever seen I found fiddly and unpleasant to use.