Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disabled text fields vs. grayed-out (opaque) but uneditable ones #142

Open
tuna-salad opened this issue Apr 24, 2013 · 0 comments
Open

Disabled text fields vs. grayed-out (opaque) but uneditable ones #142

tuna-salad opened this issue Apr 24, 2013 · 0 comments

Comments

@tuna-salad
Copy link

For example, delete a requirement and view it in the "edit requirement" panel. Notice that most texts are very hard to see compared to the requirement status, which is not disabled but grayed-out by setting opaque true. I think it would be better to make fields that don't allow editing be enabled but kept non-editable and opaque.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant