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
We have a button that allows users to open a container directly in their browser. We also have a warning that appears when their host device and Docker extension aren't on the same Tailscale network.
However, it's easy to start to ignore the big warning and treat it as a header. Perhaps we can display it less prominently in most cases, and instead prompt them in contextually relevant places. For example, when pressing "open in browser," maybe we can have a dialog that warns them that they won't be able to open the link before we pop them off to their browser?
The text was updated successfully, but these errors were encountered:
This revises the error message to clarify that Tailscale is installed
but not running, since I've confused myself a few times with the
previous message.
This could be further improved by fixing #28
This revises the error message to clarify that Tailscale is installed
but not running, since I've confused myself a few times with the
previous message.
This could be further improved by fixing #28
We have a button that allows users to open a container directly in their browser. We also have a warning that appears when their host device and Docker extension aren't on the same Tailscale network.
However, it's easy to start to ignore the big warning and treat it as a header. Perhaps we can display it less prominently in most cases, and instead prompt them in contextually relevant places. For example, when pressing "open in browser," maybe we can have a dialog that warns them that they won't be able to open the link before we pop them off to their browser?
The text was updated successfully, but these errors were encountered: