141–150 of 225 posts
Dark 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.
No PM anywhere gets credit for Dark Mode adoption in 2019. The other 2 amount to solving self-inflicted problems. You are kind.
In 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.
Earlier quoted context omitted.
lots of hn readers use slack lots of hn slack users disliked the feature lots of hn slack users who disliked the feature went straight to hn to vote up any post complaining about it that's how communities around tech broadly tend to work
a few people figured out how to change their workflow to deal with the change. turns out the same problem that exists between non-technical users and technical users exist between power-elite users and the non-PE users. when you try to show a non-technical user a different way to do things, they get really frustrated and give up easily because their entire mental model needs to change (they were used to clicking on a…
Wait, "cout" from C++? "Clout" is a real English word, I always figured it was pronounced the same minus the "l", which is neither of the versions you have there.
Earlier quoted context omitted.
The above demo works fine in Firefox, FWIW. I had a large hand in building a WYSIWYG email editor a few years back, using direct DOM editing, that was the most full featured available at the time. I would only recommend it to people with very high pain tolerance, as the differences between browsers are stark, undocumented and hard to work around.
In firefox it skips one letter at a time and maybe that is the intended behaviour, but it doesn't seem consistent with what I'd expect from a WYSIWYG editor. I'd expect there to be 2 positions between the "e" and the "t" that the cursor would stop at so I can either insert text with the formatting of "one" or "two"
Still waiting for an option to disable "drafts" (channels all of a sudden jumping to the top of the channel list)
I've been loving their responsiveness lately /s. I `ctrl-k` jump to another convo and start typing and the lag between `ctrl-k` closing and switching to the new convo is enough that I end up typing a few characters into the prior conversation - then I need to jump back to clear out the draft. Their channel listing is generally crap though, I gave up on trying to navigate it and just use `ctrl-k` jumping for everythin…
In 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…
Um, no, this is not impossible, us editor folks have been inserting 0-width space after the tag and selecting it for years. The team the size of Slack should/could have easily worked around that.
In 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…
Earlier quoted context omitted.
In firefox it skips one letter at a time and maybe that is the intended behaviour, but it doesn't seem consistent with what I'd expect from a WYSIWYG editor. I'd expect there to be 2 positions between the "e" and the "t" that the cursor would stop at so I can either insert text with the formatting of "one" or "two"
There is a position at the start of "two" in Firefox, but you have to approach it from the right. That feels sane to me.
A string that ends in *bold!*
//
AB
You can then pretty quickly see what goes wrong here:
A string that have *_italic bold_ and bold!*
///
ABC
I think you could turn any of these into interesting box forms like one of the links in this thread that has two colored boxes, and you could have text somewhere (like between A & B in the second example here) and delete that text, and suddenly not be able to get a cursor back there, short of laying some text down and reformatting it.
Markdown, and other markup/syntax based inputs, make this trivially obvious, to a large degree. (Some ambiguities in the syntax can cause issues, but those seem to be rarer than issues w/ Slacks WYSIWYG editor.)
Earlier quoted context omitted.
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.
The above demo works fine in Firefox, FWIW. I had a large hand in building a WYSIWYG email editor a few years back, using direct DOM editing, that was the most full featured available at the time. I would only recommend it to people with very high pain tolerance, as the differences between browsers are stark, undocumented and hard to work around.
Yes, I agree it should be fixed. Most WYSIWYG editors do have issues though. Just tried Pages (apple's word processor. abc def. Putting the cursor before after the space before the d I would personally think is more intuitive to insert bold but it inserts plain. As it is there is no way to type bold at the front of the bolded word. You either have to type new text and bold it OR you have to insert after the d, type a new text and an extra d then delete the leading d. Yes you can press Cmd-B then type but of course if the text had more styling applied that would get cumbersome to reapply styling so you're left with the previous solution of inserting new text in the middle and deleting the leading character.