Bug 782140
Summary: | [webadmin] a drop-down that contains only one option, should be disabled/hidden/shown as a label/?... | ||
---|---|---|---|
Product: | [Retired] oVirt | Reporter: | james labocki <jlabocki> |
Component: | ovirt-engine-webadmin | Assignee: | Einav Cohen <ecohen> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | acathrow, ecohen, iheim, Rhev-m-bugs, ykaul |
Target Milestone: | --- | Keywords: | EasyFix, Improvement |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | ux | ||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-12-20 07:33:34 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
james labocki
2012-01-16 16:10:03 UTC
Since behaviour across the application should remain consistent, general question is: when a drop-down contains only one option, should it be disabled/hidden/shown as a label/etc. -> changing the subject accordingly. (In reply to comment #1) > Since behaviour across the application should remain consistent, general > question is: when a drop-down contains only one option, should it be > disabled/hidden/shown as a label/etc. -> changing the subject accordingly. I think it really depends if you want the user to be informed about the choice we've made for him or not. An example where it's useless: when you have two hosts (the minimum for migration - but also very popular in POCs), and you migrate a VM from one hosts - there's really no use of asking to which host you'd like to migrate to - you are going to migrate from host 1 to host 2. Therefore, the whole dialog should not even pop up. It also matters if it's something that can be somehow changed later on or not. So we need to set guidelines, and treat each specific case separately, probably. Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug. |