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
The sharable ports UI is a little overly complex since we added protocol control. There are several overly implicit flows and a few duplicate methods of achieving the same result. We've had to work directly with customers already to explain the feature's usage.
I agree with @pauliuspetk we should consolidate into a single table; this was actually part of some of our original mockups. All controls would be in-line with their respective port.
Here, all listening ports would default to the hidden "Owner" and HTTP. Shared ports would be pinned to the top of the list and remain visible even if the listening port goes quiet.
The text was updated successfully, but these errors were encountered:
matifali
added
feature
Something we don't have yet
and removed
s3
Bugs that confuse, annoy, or are purely cosmetic
feature
Something we don't have yet
labels
May 9, 2024
Originally raised by @pauliuspetk here:
#11486 (comment)
The sharable ports UI is a little overly complex since we added protocol control. There are several overly implicit flows and a few duplicate methods of achieving the same result. We've had to work directly with customers already to explain the feature's usage.
I agree with @pauliuspetk we should consolidate into a single table; this was actually part of some of our original mockups. All controls would be in-line with their respective port.
Here, all listening ports would default to the hidden "Owner" and HTTP. Shared ports would be pinned to the top of the list and remain visible even if the listening port goes quiet.
The text was updated successfully, but these errors were encountered: