Assign to collections shows 0"> if not yet assigned to a collection

When I go to assign an entry to a collection, if it’s not already in the collection, it shows me a bullet item with the first line (& start of 2nd) -

0">
1 item will be permanently transferred to … will no longer own this item.

What is the 0"> meant to mean?

If it is already assigned, this bullet item becomes -

Only organisation members with access to these
collections will be able to see the items.

This is followed by the name of the collection it is assigned to.

I am running Bitwarden in Firefox on Windows. If I do the same thing in Edge on Windows, the display line is more understandable - the bullet text says

1 item will be permanently transferred to … You will no longer own this item.

@LudwigWN Welcome to the forum!

Please post a screenshot of your Admin Dashboard.

Not quite sure what you mean by Admin Dashboard.

I couldn’t determine what tags to put on the post. I’m not running any server-based things, just plain Bitwarden addin for Firefox (& Edge) on Windows 11.

The weird ‘report’ I get in Firefox (but not Edge) looks like this:

Note the text after the bullet .. ??? The characters after “transferred to” have been truncated in the screenshot, as have the line up above it (“access to t…”).

And here’s the version level in Firefox …

Ah, okay, thanks! And in that case, please use the tag server:default-cloud instead of any of the “selfhost” tags next time to avoid any confusion. (I’m going to change it for you now for this thread)

I can reproduce that on the Firefox extension.

But I would guess that this is/was a bug that was fixed.

Notice that the Firefox extension is still on 2026.5.1, while the Chromium-based browser extensions are on 2026.6.1 now, where it does seem fixed.

Thanks for the research & update.

I guess I just wait until the updated / fixed level comes to Firefox. Just annoying to see. Hopefully fix level is imminently for release.

Ha, it seems Mozilla now approved extension 2026.6.1. I just updated the Firefox extension and don’t see that error any longer.

The update with the fix has just arrived in my Firefox. Thanks once again.