Tag options cannot be deleted from the dropdown menu

[Inkqb]

Describe the bug

The “delete option” function for tags does not seem to work. Quitting the page and coming back reverses the deletion.

2021-07-29-07-42-35.mp4

To Reproduce

Steps to reproduce the behavior:

• 1. Delete a chosen tag
• 2. Quit the set view or object you did this on
• 3. Come back
• 4. It is still there

Expected behavior

A deleted tag is deleted from all objects where it was applied and does not show up in the list.

Desktop (please complete the following information):

• OS: W10
• Device: Desktop
• Version: 0.18.54

Additional context

Maybe some sort of protection for accidental deletion is warranted ?

[Inkqb]

This is still a bug in the latest version even though most bugs with tags have been resolved.

Which with the testing from before and the bugs with invisible tags that is now resolved makes for some very confusing dropdowns menus for me.

Now when you delete the tag IT DOES make the tag disapear on all pages where it was put (intended behavior I expect) but it is still visible and un-erasable from the dropdown menu.

A recording showing the issue: (deleted tags reapear in the dropdown menu when leaving and re-entering the set)

2021-08-13-14-21-01.mp4

[phileas]

Same thing here, you have to quit and re-enter the page to have them re-appear.

(nb : très bel accent )

[XxxBalCion]

Also, same here. Cant get rid of this one tag since database release.

[Kirill_Lem]

@XxxBalCion Hi! Can’t you get rid of this tag in the latest app version, right?

[XxxBalCion]

@Kirill_Lem 0.20.9 on Windows yes.

[tempapy]

Well it’s a minor bug but it was appearing in 0.21.9, seemed to be gone in 0.22.0 and reappears now in version 0.22.3 (Windows).

[kira]

Also experiencing this with version 0.25.4 on macOS (M1)

[ljunhui]

Experiencing this on 0.25.4 on Windows 10 and 11 (2 devices)

[Cernel1337]

Same issue on Anytype version: 0.25.4, Windows 11 Pro

[k.and]

Unfortunately, the issue is still present in 0.26.1.

[kira]

Still experiencing this issue as well on v0.26.1, macOS M1

[Flip]

Is this still in 0.27.0?

[sahilstudio]

Yes, still occurring in 0.27.0.

[dannyg]

Still occurring in 0.29.1 it seems.