Skip to main content

Hello, I’m experiencing an issue that makes Miro boards unusable and am trying to find a fix.

When using Safari on MacOS (v16.6), the board name field steals text input focus and will not release it unless I confirm a change to the board name. However, I can only do this on boards that I have ownership of, so on any board owned by someone else I am stuck with focus being stolen back by the board name field. 

The same boards do not have this issue with Chrome, so this is a browser specific issue. But I am not using Chrome for any other use and it is a substantial inconvenience to run a separate browser for Miro.

Clearing cache or having Editor privs on the board do not change this behavior.

This is a recent development as I have been using Miro on Safari for over a year without issue.

Is this a known or tracked issue?

Repro:

  • Using Safari 16.6 on MacOS,
  • Open a board that you have Editor privs but do not own.

Result:

  • Board name field will take focus, but you cannot change it because you do not own the board.
  • All other text input will fail, and various other functions (ex: submenus) will fail as the board name field keeps stealing focus.

Thank you for any assistance!

Hi ​@Tyson Green  I tried this on Safari with no issues - I opened a board that does not belong to me but where the link allows anyone to edit - but I noticed that I have Safari 18.6, not 16.6. Maybe try the Miro app as a workaround?

Here is something VERY interesting, however. I opened the same board in Mac Safari and Mac Chrome, and I looked at the so-called “developer console” for each where you can see internal loggings of errors. There is a huge difference. The Miro board loading in Chrome shows 10-15 errors,

 

 

But the same board while loading in Safai shows DOZENS,

 

 

I never remember seeing this many errors before . . . methinks something is not right in the state of Denmark.

Cheers, Ken

Hello Ken, thank you for this!

I guess it was as simple as updating to 18.6 (and taking the Sequoia update. Everything appears to be working fine again now.

Perhaps this will help someone else bumping into the same issue, but everything resolved for me. Thanks again!

Hi Tyson - Glad I could help!  But I am definitely writing this down in my notebook - normally I tend to give useless advice that wastes time and does not help anyone! 😀😀😀

Thanks so much for jumping in to help here, ​@Kenneth Ritley — really appreciate you sharing your insights and the workaround that solved it. 🙌

 

​@Tyson Green, I’m glad updating Safari resolved the issue! If you run into anything else or need further assistance, feel free to let us know!

🚨 Just announced: The full agenda for Canvas 25 is live! 🚨

Terms & Conditions