Editor unresponsive after exiting object in 2nd window

WHAT IS THE BUG

I stumbled across a editor / UI bug when working with multiple windows. When editing an object in fullscreen, opening a second one using CMD+SHIFT+N, and then exiting the object in window 2, the editor in window 1 becomes unresponsive. It seems like a UI bug since after reload of object in window 1, changes become visible although it seemed unresponsive before.

HOW TO REPRODUCE IT

  1. Edit object in fullscreen
  2. Create new window using keyboard shortcut. This should open the same object in second instance
  3. Check that inline commands still work in window
  4. Exit object in window 2
  5. See that window 1 no longer adds new blocks via + or \callout, \code blocks etc …
  6. I was able to provide you a video capture of the bug, here it is: Feel free to increase speed, the video got a bit long:

THE EXPECTED BEHAVIOR

Editor in window 1 should keep working.

SYSTEM INFORMATION

  • OS:
    MacOS Ventura 13.2.1
  • Device:
    MacBook Pro M1
  • Anytype Version:
    0.31.0
1 Like

This report has been added to our issue tracker and received by the Development Team.

Cant reproduce anymore in 0.31.36-beta. Maybe someone give second opinion on this. :eyes:

Should be resolved, since no one is able to reproduce. :white_check_mark:

1 Like