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
Currently we have some actions that can be perform in background even if Settings modal is open. Most important things like typing and sending messages are blocked. Others are not blocked (and probably shouldn't be) but should trigger closing Settings and they are not:
Use CTRL+k and switch channel in background - user switch channel but can't see it as Settings are still open.
If there is new message popup and the user click it it moves him to the channel in background - but as above, he can't see it because Settings are still open.
Both actions doesn't sound very bad but while we perform them "Settings" should close. In both cases user can expect that if he choose to go to the message in specific channel (point 2) or specific channel itself (point 1) he should be moved to the channel window. He actually is but can be unaware of it as Settings modal is still open.
The text was updated successfully, but these errors were encountered:
Version: 1.1.0-alpha.6
Currently we have some actions that can be perform in background even if Settings modal is open. Most important things like typing and sending messages are blocked. Others are not blocked (and probably shouldn't be) but should trigger closing Settings and they are not:
Both actions doesn't sound very bad but while we perform them "Settings" should close. In both cases user can expect that if he choose to go to the message in specific channel (point 2) or specific channel itself (point 1) he should be moved to the channel window. He actually is but can be unaware of it as Settings modal is still open.
The text was updated successfully, but these errors were encountered: