Our new text editor is now available on all communities!

Same problem here! We just had a new customer use profanity in username and he was quoted in another customers comment. Best solution would be that the quote function would check the username instead of just copying it as a text

Hi,

A problem with the contextual menu. When right-clicking below the cursor line, the menu does not display correctly (there are no copy/paste/cut options).

Example :
Here, I right-clicked on the text cursor line (where there's the red circle). We see the menu with copy/paste/cut.

Here, I right clicked below the text cursor line. There is no copy/paste/cut.
 

This happens on all browsers :)

Sure, I can: https://www.w3schools.com/css/tryit.asp?filename=trycss_table_width 

You’ll find that this example table always uses 100% width, no matter how wide or narrow you pull the window width.

Delivered

• NEW Copy/pasting URL’s from within the community will remain a URL (previously they were converted to underlined text)
  • I copied the text from the post above as example: “Sure, I can: https://www.w3schools.com/css/tryit.asp?filename=trycss_table_width “

Updates on feedback since the last update

• The best way to delete a spoiler or (nested) quote is to select the entire box (Clicking the grey resize icon in the top left of a quote or spoiler will select it. Selections can be recognized by a 2px blue line. ) and hit the backspace/delete key on your keyboard. See the spoiler below for an animated gif

  

   

   

• We’ll investigate wether it’s possible to alter the username of the person who was quoted. For now it is best to create a manual blockquote and put the username in bold above it.
• The contextual menu works as expected. It will only show relevant options (cut/copy/paste) in the line where content is displayed

While quoting in control there’s sometimes “Common” added to customers name while editing. We tested publishing the comment and it luckily didn’t follow to finished comment

Coming soon

Placeholders are coming back to your editor this Friday. Learn more about placeholders and how to change them in this post: Re-enabling editor placeholders (instruction text). 

Thanks so much for your hard work to deliver these fixes, @Yoeri and all others involved. I wanted to share this post from our super superuser – evidently it’s not possible to split up a quote that’s one long paragraph:

Here’s another example, quoting Jasper’s post above. I was able to finally splice the quoted paragraph  but it took several times pressing “Enter” and then backspacing, and then entering again.
 

@Julian if a @mention is quoted, should one receive an email notification of the quoted @mention or not?

At the moment notifications are being sent if @mention is quoted.

We have some new updates to share with you :)

Delivered

• NEW We re-enabled the editor placeholders. Learn more about placeholders and how to configure them in your community 

• Bugfix We resolved a bug for editing tables in Control. You can now add, edit and remove table cells/rows/columns

In progress

We’re working on the following items and expect to release them soon 

• Ability to add Polls to your topic

• Links that point to a webpage outside of your community (outgoing links) will open in a new tab

Next

The following items will be enhanced over time

• Replace default editor font with your company font

• Display of the @mention list on mobile

• Do not send double notifications when you’re mentioned in a quote and somebody replies to it.

Investigations update

We investigated the following feedback and came to the following conclusions:

• The editor starts writing in italics (link). We were unable to reproduce this behavior and will stop the investigation.

• Responsiveness of tables (link). We pushed a small fix that will wrap words, we won’t make additional changes to the responsive behavior of the table.

• Discrepancies between editor and final view (link). This is most probably caused by the fact that the default editor font is different than your company font. We are planning to fix this.

• Error message ‘No text’ when there was text (link). We were unable to reproduce this error state and will stop the investigation.

• “Bouncing” behavior of the editor (link). We are not experiencing this issue, but his behavior may happen depending on the browser, viewport, display settings and content inside the editor. As each scenario is unique it’s hard to resolve the specific use cases in which this happens, therefore we’re not making any changes to the editor viewport.

• Chromium doesn’t show a contextual menu (link). We pushed fixes to the contextual menu so that it opens on a regular right-click. 

• Copy/pasting.GIFs are converted to a static image (link). This is how the browser’s native copy/paste works, it can also be reproduced on other services, eg: google drive. To upload gif users can download them and use the image uploader to upload the gif.

• Selecting misspelled words moves the indicator to the beginning of the post on mobile (link). We were unable to reproduce this behavior on iOS Chrome, Safari and Firefox. We will stop the investigation.

• The letter ‘g’ is wrongly displayed. (link) We were unable to reproduce this, but we expect that replacing the default editor font with your company font will resolve this.

As this happens with different users, different machines, software combinations and so on, I’d ask you if you could still look into this? I’m using Win7 combined with Chrome on 27” 16:9 monitor with 1920x1080 resolution via HDMI cable as I write this. Zoom level is 100% and I’m not running anything that would modify the experience from my end. Every time line is changing, there’s the elevator bar in the field that disappears after the newest line gets longer. As this has been reported to us from our users, I’m obligated to deliver this request regarding this issue if you’d still check this :)