BTW, It would be nice to use COMPANY_NAME (app.company.name) setting here. I.e. you have to modify App\Utils::uiEnv() to include it.

@mollekopf, it looks good. Please, fix phpstan/phpcs issues and we're good to go.

• Simplify

• Add periodic reminder mail to degraded accounts

• Add degraded status to user:status command
• Add degraded status to some cli commands

• Fix quota/roles of a degraded user

• Browser tests

• Tests

Also, because it's likely that user will open both Add credit and Setup auto-payment dialogs. It would make sense to fetch the list of payment methods only once. I.e. it could return all methods with some type flag so we could filter it client-side.

• Fix disappearing subscribers list

• Add participants counter

• The grey status icons without the slash, do not indicate the muted state properly. Use red background here or icons with expunction element.
• Enabled (muted) sound and video buttons have different size, which is not nice.
• Screen sharing and hand button do not work. Some code still uses .text-danger to get the button state.
• Browser tests need to be modified (.text-danger class)
• Shouldn't the chat button also have the switched-on state when the chat widget is visible? The same as the hand or mute buttons.
• I think there's too many elements in gray scale, the UI looks sad.
• The chat background is too dark, the textarea does not look great with such a background.
• If you join the room as a subscriber, the mute buttons are html-disabled, but have the background set, this looks strange. I don't know maybe the buttons (not icons) should be smaller, or just should not indicate switched-on state when disabled.

• Fix subscribers list height when there's no publishers in the room

Fine with me. If this does not break any browser test assertions, then we should add some. Search for assertUserIcon

In D2269#26197, @bohlender wrote:

Is this what you want instead: https://git.kolab.org/D2281 ?

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.