Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Slack’s new WYSIWYG input box is terrible

quuxplusone.github.io

Post reply on HN
Print view View original

871–880 of 1001 posts

Re: Slack’s new WYSIWYG input box is terrible

#871

Post by sbuttgereit »

cecilpl2 wrote: post #346
sbuttgereit wrote: post #89

Earlier quoted context omitted.

That example worked fine for me, the second example (a variation on the first) worked as the article described. Once foo() was "code", I couldn't update it (at least I couldn't discover how to do so outside of killing that bit). I'd bet the first example didn't work at some point, and then was quickly patched.

The second example worked correctly seamlessly for me as well. I can easily edit text inside a code block in the WYSIWYG editor. Maybe they just patched that too?

Hmmm... possibly testing a patch... I still can't get it to work and checked for updates before trying. There could naturally be a difference in our sequence of steps, too. Once "foo()" is entered and detected as code, I can't add "bar." after the fact. I can add new code text in the middle of the detected code.

Re: Slack’s new WYSIWYG input box is terrible

#872

Post by andfrob »

Tade0 wrote: post #622
ryankshaw wrote: post #336

Earlier quoted context omitted.

what would you say are the top few out there now? looking to adopt an editor for a large website

I'm obviously biased and would probably recommend what I was working on(CKEditor), but here are some observations regarding the various propositions: CKEditor 4 excels in two things: -Handling selection - especially tables. -Editing for accessibility. I would recommend v5 though, otherwise you'd be potentially giving my one good friend, who's already very busy maintaining v4, even more work. :D https://textbox.io/ -…

To clear up some confusion around TinyMCE and Textbox.io. The products came to be under the same umbrella due to the merger of Ephox and Moxiecode. The combined company was renamed Tiny last year.

TinyMCE version 5, released earlier this year, incorporated much of the Textbox.io features and technology and is the main product moving forward. It is better than Textbox.io in almost every way now and is recommended for new projects.

Tiny did indeed raise $4M in venture capital last year. It has not been squandered by any means. In fact, we have only just started spending it as we were profitable and growing when we first raised the money.

Tiny has a good-sized development team with more than 30 people in engineering, QA, design and product management. Of the many options out there, TinyMCE is a good bet!

(disclosure: I am a founder and the CEO at Tiny)

Re: Slack’s new WYSIWYG input box is terrible

#873

Post by ajkjk »

snowe2010 wrote: post #833
misnome wrote: post #468

Earlier quoted context omitted.

Probably for the same reason people downvote when the same comment is copy-pasted all over a thread; I don't need to be linked to somewhere else in the same conversation. I especially don't need to be linked to somewhere else in the conversation that _I have already read because it is higher ranked_. Also possibly: following an opaquish link to find yourself on the very same page is annoying, and kind of the opposite…

Well I didn't copy and paste the same comment all over, I just posted this link once. The comment I linked was also not higher ranked when I commented, as I commented right around when the original post was made. Every comment in the thread was still getting shuffled around due to upvotes and nothing was stable. In the future how do you suggest I handle this?

Your comment would have been better received if it had any explanation as to why it was there, like

"someone else in this thread said that they know some slack employees and it's true: "

that way people scanning know what the link is and why it's there.

Re: Slack’s new WYSIWYG input box is terrible

#875

Post by spurgu »

tiborsaas wrote: post #418
chx wrote: post #114

The exact same happened with the draft feature. The importance of habit forming UI is very well documented, going back at least as far as Jef Raskin's The Humane Interface and the draft feature completely breaks it -- if you as much as accidentally leave a character in there, you can't find the channel/DM at its normal place. Despite repeated calls to make it optional, nothing. Threads are also broken, has always bee…

What's wrong with the drafts feature? I tend to use it if I'm messaging someone and I don't have all the info yet or I might have forgotten to reply :)

Or if you get a more urgent message that you really need to reply to while typing.

Re: Slack’s new WYSIWYG input box is terrible

#876

Post by 0xffff2 »

syshum wrote: post #575
sharken wrote: post #524

Earlier quoted context omitted.

Not until Microsoft Teams gets the layout fixed, see https://microsoftteams.uservoice.com/forums/555103-public/su...

Not really. Teams biggest "Feature" is that is part of the Office 364 Suite, a lot of the layout and other issues are simply forgiven since there are no additional licensing or costs to use it over Slack if you are already on Office 364 Enterprise Teams is "good enough" for most organizations and is improving, That is microsoft current plan, be "good enough"

Yep. My large, distributed government agency was a free-for-all for several years. After letting everyone try things out, they've now decided to standardize on O365 and dozens of team-specific Slacks are getting torpedoed in favor of the agency-wide Teams instance.

Re: Slack’s new WYSIWYG input box is terrible

#877

Post by rbetts »

ninkendo wrote: post #801

Did Slack ship a buggier version of this yesterday? I have it on one of my workspaces, and it's fine . I can still type `backticks` in the editor, with the exact same combinations of keystrokes I used before, it's just that they render as they will on the channel, rather than showing me the backticks (and only when I type the closing backtick. GIF here: https://i.imgur.com/o3wPWN0.gif ) Triple backtick does the same,…

Or try to type nested bulleted lists.

Re: Slack’s new WYSIWYG input box is terrible

#878

Post by exolymph »

avdempsey wrote: post #831
jonahx wrote: post #810

Earlier quoted context omitted.

Many edge cases are different. To name one: You realize after finishing your code block that the first two lines of it actually shouldn't have been part of the code block, but should have been normal text above. Go ahead and try to make this change with the new system. Compare that to what you would have done with the old, plain-text system.

Sure enough, the rich text formatting is copied. The workaround I have for this is the Get Plain Text app. It strips all formatting from copied text (either automatically or on a keyboard shortcut). Sad it's required for this use case. But at least this works.

On MacOS, paste-as-plaintext is Ctrl+Shift+V

(Or I guess Cmd+Shift+V)

Re: Slack’s new WYSIWYG input box is terrible

#879

Post by taormina »

asix66 wrote: post #790
nmec wrote: post #701

Earlier quoted context omitted.

I expressed my discontent to them as well and just received this reply: "I'm afraid there is no way to disable this at the moment, and it's not in the roadmap to roll back on this feature. That said, we're still in the initial stages here, so our focus right now is listening to feedback as we consider certain changes for improvement as we move forward. You've raised some fair points here, so I've shared your feedback…

So their rollout methodology here was to go live with beta software, on production servers, to paying customers, and force them to find the bugs. Brilliant!

They deployed it as an A/B test[0]. Which means they are blatantly lying about being able to roll it back.

[0] https://github.com/kfahy/slack-disable-wysiwyg-bookmarklet/b...

Re: Slack’s new WYSIWYG input box is terrible

#880

Post by 0xffff2 »

kelseydh wrote: post #355
igetspam wrote: post #327

Earlier quoted context omitted.

This is why I heavily advocate for not using Atlassian products. I use the "can't trust Australia" statement as a supporting argument but the terrible editor is what started my crusade. My company uses Jira but I do all my tracking in Clubhouse. We have Confluence but most of us write docs in Google Docs because it's less painful. I recently got us moving away from Bitbucket too. If Slack stands by this change (like…

100% agree that Clubhouse > JIRA. If I hear a company uses JIRA, I will actually question whether I want to work there.

My organization uses all of Atlassians products. Every time I as for a sane alternative and get shot down I question whether I want to work here.
Post reply on HN