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
{{ message }}
This repository has been archived by the owner on Mar 23, 2019. It is now read-only.
When viewing a specific task and wanting to navigate back to its associated task group, my first instinct is to click on the ID of my task group as listed under the "Task Group ID" heading. However, I quickly realize that that text isn't a link, and that I have to specifically click on the "link" button on the right.
I feel like conventions on the web usually have text act as links, and buttons are used to perform other operations (e.g. copy, edit, etc). Using a visual button to act as a link seems to run against the standard conventions of the web a little bit.
🍎 for 💭 ? 😄
The text was updated successfully, but these errors were encountered:
You can still select the text by starting your selection outside the text (to the left/right), then selecting the text. Once selected, you can copy like normal
There's a "copy" button on the right already. Since both actions already exist as buttons, I feel that we're safe to make the task ID text behave as conventional-to-the-web as possible, maybe?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When viewing a specific task and wanting to navigate back to its associated task group, my first instinct is to click on the ID of my task group as listed under the "Task Group ID" heading. However, I quickly realize that that text isn't a link, and that I have to specifically click on the "link" button on the right.
I feel like conventions on the web usually have text act as links, and buttons are used to perform other operations (e.g. copy, edit, etc). Using a visual button to act as a link seems to run against the standard conventions of the web a little bit.
🍎 for 💭 ? 😄
The text was updated successfully, but these errors were encountered: