Skip to main content

I use Windows 11 and the installed Miro application v. 0.10.80.

When I edit a simple text like this …

… it happens that the Enter button stops working and I cannot add additional lines.

I could not figure out what triggers the problem.

When I close the Miro App and start it again, the problem is solved – until next time.

Yesterday it happened 3-4 times within 30 minutes so it becomes annoying and disruptive for creativity.

Someone who has seen that issue?

Hi ​@Frank Kardyb Jessen,

 

Thanks for reporting this issue! I can see how this would be frustrating, especially when it disrupts your workflow. Since restarting the Miro app temporarily resolves it, it might be helpful to check the following:

  1. Ensure you're using the latest version of the Miro app. You can download the latest version here.

  2. If you’re using any custom keyboard layouts or language settings, try switching to the default English (US) layout and see if the issue persists.

  3. If you haven’t already, see if the issue occurs when using Miro in a browser (Chrome, Edge, or Firefox).

  4. Try clearing the Miro app cache or reinstalling the app to rule out any corrupted files.

If the issue persists, I recommend contacting Miro Support with details on when it happens and any patterns you’ve noticed.

 

Let me know if anything changes! 🚀

 


@Frank Kardyb Jessen - I am currently using version 0.10.87.0 on Windows 11 and am not experiencing the issue. I also see that, when going to https://miro.com/apps, there is an even later version (0.10.93.0).


I have just installed the latest Miro client - will see if this does fix the issue ...


Unfortunately the problem persists after updating Miro to latest version.

The green bar on the snippit below is my cursor position. Hitting Enter does not produce a new line as it should - nothing happens.

After closing/restarting Miro it works again - untill next time.

Enter key stops working when editing bulleted text fields

 


Thanks for the additional details, ​@Frank Kardyb Jessen.

 

It sounds like something is intermittently interfering with how the Enter key is registering in Miro’s text editor. Since restarting the app temporarily resolves it, this could be tied to a caching or input handling issue in the desktop app.

 

If the issue persists, I will convert your post to a support ticket


@Eca - I am experiencing the same issue. Actually, there are a few things going on.

The first thing I noted is that, after creating a mind map node, I then appear to lost the ability to press enter in a text object.

 

I noted that the mind map node text context menu is now showing lists (numbered and bullets) as an option where we previously had to type a hyphen and then a space to start a bullet (or 1. to start a numbered list). Then, you would use Ctrl/Cmd + Enter to start a new list item - this is outlined in the mind map HC article:

To create a bullet-list in a node, type and press the spacebar. To create a numbered list, type 1. at the beginning of a line.
To create a bullet list starting from the second (or third/fourth/etc.) line, create a new line with Cmd + Enter (for Mac) or Ctrl + Enter (for Windows).

Note: The associated GIF appears to be incorrect.

Before this change (around five months ago) there was a bug (#765990) outlined in this post where pressing Enter created an unexpected new line. Perhaps that was the result of preparation of this change with lists in mind map nodes, however something has been missed as the two behaviours are not lining up. My expectation is that, when pressing enter while in list mode in a mind map node, a new list item is created.

I will report this to the support team and will update this post as I hear back.


I can reproduce the problem just by clicking an existing mind map node.

After that I cannot add lines to my bulleted list.


Update from Miro support – issue is resolved:

I want to confirm that there was indeed a bug on our side, which caused the Enter key to stop working in Text objects. Our engineering team has just released a fix for this issue. 


Problem solved - Thanks 😊


Reply