Maybe we should apply it anyway, and revisit again now that we have even more buttons (hand and channels) in the toolbar.

As for the chat icon and status icons change I'm ok with this. But I'm not sure about the rest.

The idea was to hide the menu/footer inside the room, i.e. after joining in, but room setup screen should have the menu as usual. I also don't like making component/page specific exceptions in the Menu widget. I would probably do it with css. Also the code added in Room.vue asks for some deduplication, i.e. we need a method on the $root component that could be re-used as we have the same code in at least two places now. Not to mention that in this state some browser tests will fail (but I didn't check yet).

• Add forgotten component

Rebase

• Remove redundant condition

I'll review this again regarding 422 handling.

A couple of browser tests need to be modified in tests/Browser/UsersTest.php

And of course some tests will be needed.

• Fix type hint

-fix

The disabled attribute value could be boolean not string, but it will work either way.

• Cleanup
• Simplify resize() calls
• More tests
• Test updateConnection endpoint
• Media setup dialog
• Fix test regressions
• Add tests for media setup dialog
• Fix connection role propagation to new connections

• Rebase

• Add missing migration file

I've found one issue. The role change is not propagated to new connections. Scenario:

1. User1 joins as a subscriber
2. Moderator promotes him to a publisher
3. User2 joins and sees a UI issue, because the User1 tail is a subscriber-like tile, and there's a video element of User1 "out of the matrix".

• Add tests for media setup dialog

• Fix test regressions

• Media setup dialog

If you think that this internal cache is not really needed then go this way and remove use of self::$typedata. In rare cases when we list folders for all folder types separately in a single request, we'll end up with several requests to the Roundcube imap cache, instead of one. I'm afraid that we might call folder_typedata() or folder_type() methods quite a lot, but I didn't check that, so I'm not sure.

• Cleanup
• Simplify resize() calls
• More tests
• Test updateConnection endpoint

How about we call self::folders_typedata($prefix); to populate the cache, but then user folder_type() anyways to fetch missing entries (it still uses the cache if available)?

With this change METADATA for every folder will be asked separately. This definitely will have performance implications. Maybe a better approach would be to add a method to reset kolab_storage::$typedata (and other cache-like data if needed). And call that method from syncroton's kolab_sync::sleep() or kolab_sync_backend_folder::hasHierarchyChanges().

• Fix typo

• Improve constants handling
• Add unique key on openvidu_connections.session_id
• Fix: session_id should be indexed but not unique
• Remove redundant where clause

Wouldn't global STATUS_FOLDER_HIERARCHY_HAS_CHANGED status be more appropriate? Or this does not work with Outlook?

This code is not supposed to be used by Kolab backend. We're using kolab_sync_backend_state::validate().