You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If I bookmark a room and save it, all is fine but if soon after I try to bookmark another room I get the same info of the previous room. It happens if I click the little bookmark icon on the right of each room and with the hamburger menu on top right of the window.
To Reproduce
Steps to reproduce the behavior:
Bookmark a room in any way offered by the UI
Add bookmark name, set username and tick to join at startup
Save
Try to bookmark a different room
The window which opens has the same exact info of the previously bookmarked room (i.e. it doesn't update with new info)
Environment (please complete the following information):
Desktop
Browser Chrome current release (109.0.5414.120 (Build ufficiale) (a 64 bit))
Converse.js version 10.1.0 running with the following setting: conversejs_resources = "/usr/local/lib/prosody/modules/mod_conversejs/dist"
as a prosody module
Prosody 0.12.2-1~bpo11+1 on Debian Bullseye
conversejs_tags = {
-- Load libsignal-protocol.js for OMEMO support (GPLv3; be aware of licence implications)
[[<script src="https://cdn.conversejs.org/3rdparty/libsignal-protocol.min.js"></script>]];
}
conversejs_options = {
locked_domain = "woodpeckersnest.space";
auto_focus = true;
view_mode = "fullscreen";
}
The text was updated successfully, but these errors were encountered:
Describe the bug
If I bookmark a room and save it, all is fine but if soon after I try to bookmark another room I get the same info of the previous room. It happens if I click the little bookmark icon on the right of each room and with the hamburger menu on top right of the window.
To Reproduce
Steps to reproduce the behavior:
Environment (please complete the following information):
conversejs_resources = "/usr/local/lib/prosody/modules/mod_conversejs/dist"
as a prosody module
The text was updated successfully, but these errors were encountered: