Re:GitHub staff are required to use Teams by Sep 1, 2023
by vladvasiliu on Monday February 13, 2023 @03:27PM
(#34779869)
> When joining a video/audio meeting, even though the "Join" button is colored like it's active, hitting enter will pull up some part of the audio or video config instead of joining the meeting.
This gets me every time. Even more so recently when, for some reason, it started to take its sweet time actually joining meetings.
Someone will invite me to join, I'd click join in the popup and go about my business. Since it's slow, I'm not too bothered if I don't hear anything right away. Then the person will message me along the lines of "so... are you joining or what?
Re:GitHub staff are required to use Teams by Sep 1, 2023
by hulitu on Monday February 13, 2023 @04:12PM
(#34780601)
Welcome to the new UX/UI/Web x.0 whatever.
Why, in the name of ... , when only 1 (one) input field is displayed on the screen, why it is not active ? 20 years ago this was the standard. What happened ?
Re:GitHub staff are required to use Teams by Sep 1, 2023
by giantrobot on Monday February 13, 2023 @06:21PM
(#34782459)
"I added the .active class to the div! What more do you want?!"
When joining a video/audio meeting, even though the "Join" button is colored like it's active, hitting enter will pull up some part of the audio or video config instead of joining the meeting.
Messages will remain "unread" until a tab is selected and then clicked in. I have to interact with the fucking tab with the cursor before it will recognize I read a stupid message.
These UI issues are amateur hour shit. I run into them dozens of times a day because my fingers are on the keyboard and I like to use keyboard shortcuts. Using Teams requires not just a mental context switch but a physical adjustment to simply send a reply or just mark a message as read.
This is all besides Teams spinning up my fans with 300% CPU usage for reasons.