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
[2.0.5-alpha.15]
I think it would be better if the SMA Update Channel field wasn't text-editable.
Unless there is actually secret channels that can only be accessed that way.
In which case.... never mind, just silently delete this issue ¯_(ツ)_/¯
Otherwise I think it would be more sensible if this was a greyed out field.
The arrow should not have to be hit specifically to get to the drop-down. It should suffice to hit that field anywhere and trigger the dropdown.
Similarly weird for keyboard users who select the field and use down-arrows to switch between channels. They won't see all available channels at once, which is confusing.
Also they'll see the channels with a blue text-background, because they are text-selected, which is also confusing.
Here is a positive example in TheBrain 11 of how I could be done differently:
[2.0.5-alpha.15]
I think it would be better if the SMA Update Channel field wasn't text-editable.
Unless there is actually secret channels that can only be accessed that way.
In which case.... never mind, just silently delete this issue ¯_(ツ)_/¯
Otherwise I think it would be more sensible if this was a greyed out field.
The arrow should not have to be hit specifically to get to the drop-down. It should suffice to hit that field anywhere and trigger the dropdown.
Similarly weird for keyboard users who select the field and use down-arrows to switch between channels. They won't see all available channels at once, which is confusing.
Also they'll see the channels with a blue text-background, because they are text-selected, which is also confusing.
Here is a positive example in TheBrain 11 of how I could be done differently:
The mouse here can click anywhere into the field.
Here's some more of this behaviour:
https://www.loom.com/share/e60fd7cb471d49b4a3f9111c08fa359a
PS: This is neither a bug nor a feature request. Maybe allow the reporter an "Enhancement"-option for issue creation?
The text was updated successfully, but these errors were encountered: