Skip to main content

We are very proud to announce that our completely new editor is now available for all users on all communities! :grin::raised_hands::pencil2: We have invested a lot of time to give you and your users more options to create richer content in an easy way - so we hope that you will enjoy working with the new editor as much as we do!

We are investigating line-height / spacing inconsistencies as well as problems with selecting text on some viewports (e.g. Safari on iOS).

Polls are temporarily not available, but will be added again soon.

 Overview of improvements

There are many things which have improved with the new editor, just to name a few:

Improved existing features

  • Image upload
    • Drag & drop images into the editor instead of manual upload
    • Captions (descriptive text underneath uploaded images)
  • Code
    • In-line code is now possible (previously code was in an extra line)
    • Code syntax (code is not being stripped automatically anymore)
  • Lists
    • Multi-level lists are possible now
    • Better UX in working with lists (previously lists could not be interrupted by line breaks)
  • Text styling
    • Text styling within lists was not fully supported before

New features

  • Tables!
  • Callouts
  • Text color / background color
  • Horizontal lines

Of course not all of these features are available to end users, some of these (e.g. text color, header, callouts) are only available in the Control environment for now. We have plans to make this available to front-end users via user roles in the future, so that you are in control of who can make use of these features - please share your thoughts on this with us in the comments!

Feedback

Please let us know what you think of this improvement, also how your users are feeling about it. This way we can adjust and improve the editor even further in the future!

Feedback on previous posts

  • The new editor has 2 different scenarios as it comes to adding an image: 1) Insert image will directly show the image in the content and 2) Upload files will attach an image to the post. It is correct that you no longer can select an image from your hard-drive an both insert it into the text and attach it. We deliberately choose for the new set up as it makes more sense to choice up front wether you want to 1) insert a photo or 2) attach a photo
  • @LPortalupi have you tried to post an URL that does not include your primary domain (coursera) and see if that does open a new tab. The way this functionality behaves is that it looks at the domain name of your community and all links with the same structure will open in the same tab

This was the last update from my side for a short while as I will be out of office the coming time. If you have any questions, feedback and ideas still do not hesitate to let us know, my colleagues will be happy to help and support :)

 

Actually the links in that example post I linked to were bit.ly links, and they opened in the same tab. I just tested this with another post’s link to a different Coursera.org page and it opened in a new tab. This seems to be inconsistent; it doesn’t seem like expected behavior.


Hi @Julian, thanks so much for stepping in while Yoeri is away! I wonder if you could also make sure this issue is addressed. I’m happy to provide more info if needed (or file a support ticket) – I just don’t want this to be overlooked. Thank you!

Hey @LPortalupi!

Yes, I was already looking into it, but I was first not able to figure out the status of this. Luckily I have the right information now:

  • For replies, new questions, ideas and discussions, the behaviour described by Yoeri does apply: Same-domain links open in the same tab, while external domains open in a new one
  • For new articles however, there seems to be a small issue, where all links open in the same tab, regardless if same-domain or external

The team is already working on a fix - it seems to be related to the same cause of the issue that causes line breaks not to be displayed in the article preview (reported by you earlier). So hopefully both of these items will be fixed very soon! Will share it with you once I see that it has been resolved.

Hi all,

quick update from our side:

Custom fonts in editor

We have now fixed an issue where custom fonts were not displayed in the editor box, instead the default font was displayed.

Of course we are working on more improvements in the meantime, stay tuned for further updates.

Hi all,

quick update from our side:

Custom fonts in editor

We have now fixed an issue where custom fonts were not displayed in the editor box, instead the default font was displayed.

Of course we are working on more improvements in the meantime, stay tuned for further updates.

Hi @Julian. The font when typing a response in our community is extremely light – it’s not showing up in the same way as it appears in published posts. I’m guessing I need to do something on my end to fix this – could you please let me know what’s needed? Thank you.

 

Hey @LPortalupi,

thanks for raising this! I have spoken to my colleagues and they found a discrepancy in the setup of fonts - a different font version was used for both elements, hence the difference.

They have changed this now, so it should be fine now:

Please let me know if there is anything!

It’s fixed – thank you, @Julian!

Hi, not sure if I should keep adding to this thread? Our star superuser has reported another frustrating experience using the quote feature. Sharing screenshots here as she does a great job explaining it:

Here she introduces what the issue is
And here’s the example

 

Also, just encountered this issue when using the text editor to create a post here in inSpired. My cursor is bumped back up to the top of the post as I’m trying to add content after the emoji:

 

I’ll also keep adding these here as I just happened to receive complaints of this editor on edge. It looked like this to our superuser:

 

 

She is using Edge, typically with larger fonts as she is a senior citizen 🙂 She said that when she types more text the scroll bar does not move.

Thanks for your feedback, please do keep reporting them in this topic so that we have everything centralized.
 

Our star superuser has reported another frustrating experience using the quote feature. 

Splitting up a quote with a numbered list into multiple quotes will always reset a numbered list to one. This is how the technology (html) behaves, when you split up a quote you are literally closing a quote element (and closing the numbered list inside it). The new (splitted) quote is treated as a new element, and so is the numbered list inside it, therefore it will start at 1 again. We can not change this behaviour. In this case we would suggest using unordered / bullet lists. 
 

My cursor is bumped back up to the top of the post as I’m trying to add content after the emoji:

This should not happen, we haven’t seen this behavior before. Does this happen every time you add an emoji in your post or does it happen sometimes?
 

She said that when she types more text the scroll bar does not move.

The scroll bar shouldn’t be there in the first place :wink: What kind of content is she writing in the photo that you shared, it doesn’t look like a default paragraph


 

She said that when she types more text the scroll bar does not move.

The scroll bar shouldn’t be there in the first place :wink: What kind of content is she writing in the photo that you shared, it doesn’t look like a default paragraph

Hi @Yoeri ! What you see in my photo is the placeholder, so she has not (yet) typed in anything when she took that screen capture.

Another user had reported during the weekend, that they are facing the same problem when the browser window is 882-1030 pixels wide. They were using Firefox 70.0.1 (32-bit) on Desktop.

Edit: I was able to verify this:

 

 

I was able to reproduce this as well, thanks for the detailed information. I will file a bug report and inform the development team :)

 

@-mention in quotes

@Suvi Lehtovaara& @LPortalupi:

So I have shared your feedback that the initial fix of this issue is not working (in some cases?). My colleagues have created an investigation ticket to see what is wrong exactly, so that they can resolve this as soon as possible. Thanks for reporting this to us.

 

The engineers finished investigating and they can confirm now that the issue is fixed. They found out the issue happened with mentions in nested quotes, as the @mentiones weren’t parsed as part of a quote (text), and the system would only see them as mentions, hence the notifications were triggered. 

This should be a great test - to see if Suvi and Laura received notifications this time. :flashlight:

I've tested it yesterday on our community with two superusers who noticed it before, they didn't receive a notification mail about a quoted mention. I mentioned them today to check if they still received that and that was the only notification they received. It seems fixed :slight_smile:

Thank you @Jasper for the confirmation! Really glad to see it solved :smile:

I get pretty annoyed when trying to edit a text with colors on front end, which makes the colors disappear. It's because the editing permissions I have in Control and front-end aren't equal. Will this be fixed in a future update?

Hi @Jurgen ! Yes it will be fixed, the team is aware of this issue and there is a ticket in the backlog to address it. 

Good to know :)

I get pretty annoyed when trying to edit a text with colors on front end, which makes the colors disappear. It's because the editing permissions I have in Control and front-end aren't equal. Will this be fixed in a future update?

We enabled text- and background colors in the community editor. This should resolve the issue mentioned above :)


 

She said that when she types more text the scroll bar does not move.

The scroll bar shouldn’t be there in the first place :wink: What kind of content is she writing in the photo that you shared, it doesn’t look like a default paragraph

Hi @Yoeri ! What you see in my photo is the placeholder, so she has not (yet) typed in anything when she took that screen capture.

Another user had reported during the weekend, that they are facing the same problem when the browser window is 882-1030 pixels wide. They were using Firefox 70.0.1 (32-bit) on Desktop.

Edit: I was able to verify this:

 

 

@Yoeri  any updates on the fix of this bug? Our superuser is very disappointed as this really hinders her use of the community. 

@Yoeri  any updates on the fix of this bug? Our superuser is very disappointed as this really hinders her use of the community. 

We are aware of the issue and have a ticket in the backlog to investigate and resolve this :)

And another question: What editor are you planning on using for private messages? Until now, there is the old editor in action.

Almost missed that one. :)

So as far as I know, the private message text editor is (much) harder to replace with the new editor due to the way it is implemented in the platform. Of course we want all editors to be the same, however this one we had to postpone - due to the amount of extra work.

@Julian any update or ETA for the new editor in private messages? I have a vague memory of December, but that must be a dream I had? :see_no_evil:

Hey Suvi!

I am afraid you have been dreaming with the ETA. :stuck_out_tongue_winking_eye:

Unfortunately, we have not yet fully commited to implement the new editor into the private message feature... BUT we have planned to actually investigate this specifically, we will know more about this by the end of this month.

Again of course I know that this would be a big improvement in many ways (attachments, images, etc.) and help all of us running support via the community. Me or Yoeri will be able to give you more concrete (and hopefully positive) info about this once this has been completed. :)

 @Julian , roger that!

 

 

Small update, we deployed a fix to the editor that should prevent a horizontal scroll bar in the editor [link to feedback] @Suvi Lehtovaara 

Terms & ConditionsCookie settings