Can't open objects in list view

WHAT IS THE BUG

When you have a set and use the List View, clicking on an object doesn’t open the page. But if you click behind the last visual relation or object name it does open the object.

The “hitbox” coördinates seem a bit off. For a lack of better words on my part.

HOW TO REPRODUCE IT

  1. Go to any set
  2. Set the view as List
  3. Try tp click on any of the objects in the list
  4. See nothing happening

THE EXPECTED BEHAVIOR

Expect to open an object when clicking on it, not expecting it to open when clicking behind it.

SYSTEM INFORMATION

  • OS:
    Windows 10
  • Anytype Version:
    v.0.32.2

ADDITIONAL CONTEXT

Confirmed on 0.32.2 (I think that is what @Jeroen is running, too :slight_smile: )

1 Like

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

1 Like

Indeed, changed it.

Does the video work btw? I saw it ones now it’s doesnt work anymore hehe

1 Like

WHAT IS THE BUG

Clicking on the name of an object in the List view doesn’t open the object.

HOW TO REPRODUCE IT

  1. Go to a set with objects
  2. Change view to “List”
  3. Click on the object’s name
  4. Nothing happens
  5. Click on the empty space after the object’s name
  6. Object is opened in a popup

    (Clicking on the “Today’s meeting notes” does nothing, clicking on the empty space next to it opens the object)

THE EXPECTED BEHAVIOR

Object should be opened by clicking on the name in the list view.

SYSTEM INFORMATION

  • OS:
    Windows 11
  • Anytype Version:
    v.0.32.2

Confirmed on Linux appimage v0.32.2.

Besides list view, I was also able to reproduce it with gallery and kanban view. Can anyone confirm?

Clicking somewhere outside of the object name seems to open it correctly.

Edit: fixed in 0.32.3. Thanks team!

Bug confirmed by the Anytype team, and should be fixed in an upcoming release

1 Like

This issue has been fixed by the Development Team and will be implemented in an upcoming release.

1 Like

This issue has been fixed by the Development Team and will be implemented in an upcoming release.

This issue has been fixed by the Development Team and will be implemented in an upcoming release.